Ms dns not updating
Ms dns not updating
The DHCP client will communicate with the authoritative DNS server directly for updating its A record, but the DHCP server updates the DNS server with the client’s PTR record In some cases, a DHCP server may update a client's A record on its behalf, even if the client did not specifically request this.This can occur with non-Windows machines that may not be able to request dynamic updates.
The most commonly reported symptom is that clients cannot resolve A or PTR records for other client machines while using the VAs or the Roaming Client for DNS resolution.
Statically-set clients (static clients) that perform dynamic updates will send updates for both its A record (forward lookup record) and its PTR record (reverse lookup record) to the authoritative DNS server.
Clients with dynamically-set network connections (DHCP clients) will communicate with both the authoritative DNS server and the DHCP server for updating A and PTR records.
Note: “This is a modified configuration supported for DHCP servers running Windows Server 2008 and DHCP clients.
In this mode, the DHCP server always performs updates of the client’s FQDN, leased IP address information, and both its host (A) and pointer (PTR) resource records, regardless of whether the client has requested to perform its own updates.” “With secure dynamic update, only the computers and users you specify in an ACL can create or modify dns Node objects within the zone.
From there, the client continues communicating with the primary DNS server that is accepting the PTR record update.
Please see For a DHCP client, when some particular action causes its IP address to change, such as a DHCP lease renewal, if the client supports it, it will send Client FQDN information (DHCP option 81 flags) to the DHCP server.
This is because DHCP doesn’t own the record, the client does, even though DHCP registered it.
The way to get around this is you can configure DHCP’s Option 081 to update the record for all client, no matter if the client asks or not.
riginally posted this in 4/2006, and updated throughout the years, but I still get questions from time to time asking why updates are not working, especially PTR.
Well, I thought it’s time for an update and to just offer a summary in the beginning, because in this day and age, no one wants to read!
Please see For a static client, the client will communicate directly with the authoritative DNS server to update its PTR record.