Imagine if an important server's DNS A record suddenly gets changed to the wrong IP. DDNS can sometimes go on a walkabout and it's important to know where to start troubleshooting if this happens.
Let's demonstrate a typical troubleshooting scenario that you may come across with DDNS.
We have multiple hosts as of late that sucessfully pull a DHCP address and are domain machines that there is no A record being created for the host.
I can do a reverse lookup on the IP and that works but not name to IP.
A quick Facebook read the first line and click “Like,” seems to be the norm. And yea, I had to state Windows 2000 and newer, because this stuff doesn’t apply to older Windows versions.
Well, I will also offer the nitty gritty below the summary for those who want to read. But DHCP will register its PTR (reverse entry) record.
When DHCP is used to allocate IP addresses, the default configuration is shown below—which tells the DHCP server to register records in DNS on behalf of clients only if requested to do so by the client or if the client is unable to dynamically register (e.g., Windows NT 4.0).
If you're not familiar with how DDNS and AD work together, you may not realize just how many moving parts there are with this product (check out Understanding Dynamic Update from Technet to learn more).
When one link in the chain fails, records may stop getting updated or may even get removed altogether inadvertently!
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.