We have a network with a segment for client machines that uses a couple of Windows 2008 R2 servers for DNS and DHCP (all AD-integrated).Clients are mostly Windows 7 machines with a few XP and Vista.The DHCP server is setup to always update both A and PTR record.The problem is that the PTR aren't actually updated and, sometimes, the A record isn't either.Domain Name System (DNS) client computers can use dynamic update to register and dynamically update their resource records with a DNS server whenever changes occur.This reduces the need for manual administration of zone records, especially for clients that frequently move or change locations and use Dynamic Host Configuration Protocol (DHCP) to obtain an IP address.This is designed so that if a change to the IP address information occurs, corresponding updates in DNS are performed to synchronize name-to-address mappings for the computer.
For example, supposethat a client named oldhost is first configured in System properties with the following names.
When you directory-integrate a zone, access control list (ACL) editing features are available in DNS Manager so that you can add or remove users or groups from the ACL for a specified zone or resource record.
Hello everyone, I have a strange problem and I can't seem to see anything that could cause it.
Updates result in actual zone changes or increased zone transfer only if names or addresses actually change.
When the DNS Client service registers host (A) and pointer (PTR) resource records for a computer, it uses a default caching Time to Live (TTL) of 15 minutes for host records.