Dns not updating records from dhcp
DNS servers provide domain name resolution for network resources.
They associate the TCP/IP address assigned by DHCP to a client with its fully qualified domain name (FQDN).
The DNS Client service performs this function for all network connections on the client, including any that are not configured to use DHCP.
When a qualified DNS client (such as a computer running Windows XP Professional or Windows Vista®) issues an update, DHCP servers running Windows Server 2008 process the update to determine in which of three ways the server will initiate updates on behalf of the client: The ability to register both A and PTR resource records enables a DHCP server to act as a proxy for clients running other operating systems, such as Microsoft Windows Millennium Edition, or Windows 98, for the purpose of DNS dynamic update registration.
However, the reverse DNS entries ("PTR" Records) are not.
The reverse lookup zone exists, and I can add entries to it manually, but it doesn't automatically populate.
The Domain Name System delegates the responsibility of assigning domain names and mapping those names to Internet resources by designating authoritative name servers for each domain.
You should apply the information in this topic only to computers that have had the Dynamic Host Configuration Protocol Best Practices Analyzer run against them and are experiencing the issue addressed by this topic.Then check the Security tab on the Reverse Zone and make sure that group is authorized to create all child objects (DNS records) 2) If your statically-configured hosts are not updating the reverse zone, make sure their NICs are configured to register their IP in DNS (Windows hosts are enabled for this by default).I've stumbled upon a strange behaviour with Windows machines, which seems to be fairly consistent between all Windows versions from Vista/2008 to 8.1/2012 R2; it doesn't happen instead when using Windows XP or Windows Server 2003.Dynamic updates are enabled for both the forward and reverse zones. This could be due to a couple of different things: 1) Are your clients obtaining IPs via a Windows DHCP Server?If so, your DHCP server may not be configured to auto-register their IP with the DNS server.