Dns not updating records from dhcp
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.
If it's started, ensure there's no events in the computer's System event log that indicate a problem. Check the advanced DNS client NIC setting The "Register this connection's addresses in DNS" should be on by default, but we've seen instances where it's disabled through some kind of policy.
This must be checked for the DDNS process to proceed.
It's hard to imagine having to manually add and remove DNS records as fast as machines are constantly getting replaced in most IT organization these days.
When DDNS is working properly it's wonderful, but when it fails it can sometimes turn into a major pain to troubleshoot.
You just replaced a computer; the old computer is off the network and had held the DHCP IP address of 192.168.0.10.
If this service is stopped for some reason no update will proceed.
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!
There are a few other settings that must be correct on each client as well.
Microsoft Dynamic DNS (DDNS) is a wonderful feature.
Combined with Active Directory (AD) it makes managing thousands of DNS records for clients and servers a breeze.