Dhcp server not updating dns records

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.

Microsoft is conducting an online survey to understand your opinion of the Technet Web site.

Secure dynamic update can prevent a client from creating, modifying, or deleting records, depending on the ACL for the zone and the name.

By default, secure dynamic update prevents a client from creating, deleting, or modifying a record if the client is not the original creator of the record.

For example, if two computers have the same name and both try to register their names in DNS, dynamic update fails for the client that registers second.

You can approach this by manually forcing the clients to check in.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.For more information about best practices and scans, see Best Practices Analyzer ( The DHCP server will not register DHCPv4 client names in DNS resulting in the inability to connect to these client computers using hostnames unless the client computers are themselves registering DNS records.When DHCP changes IP address information, corresponding DNS updates synchronize name-to-address associations for the computer.When a DHCP server registers and updates DNS pointer (PTR) and address (A) resource records on behalf of its DHCP-enabled clients, it uses the information contained within an additional DHCP option: the Client FQDN option (option 81), which permits a client to provide its FQDN and any instructions to the DHCP server that is used to process DNS dynamic updates on its behalf.