Windows server 2016 dhcp not updating dns

Dynamic DNS is a feature that allows hosts to register their records in DNS, thus removing the need for administrators to manually create records.

In addition, Secure Dynamic Update can be required for zones that are Active Directory-integrated (and should be required, per best practices), which allows only members of the Authenticated Users group to register records.

When a DHCP server is added to the Dns Update Proxy group, its records aren't secured, meaning that other DHCP servers can update the records.

In additon, hosts can change the records and then become the owner of the record.

Leakage of private DNS updates is caused by inconsistent configuration between DNS servers and DHCP client/server entities.I can use nslookup and it shows the server and the address fine.These machines seems to be working fine, but I cannot ping or rd to any computer by name.Q: Does setting DNS dynamic update credentials on DHCP achieve the same result as adding a DHCP server to the Dns Update Proxy group?A: The short answer is no; however, it's important to step back and understand how DNS interacts with DHCP regarding dynamic updates, then look at what each of the two actions mentioned in the title actually does—namely, setting DNS dynamic update credentials on DHCP and adding a DHCP server to the Dns Update Proxy group.

Leave a Reply