Active Directory’s DNS Domain Name is NOT a single label name ("DOMAIN" vs.
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.
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!
Keep in mind, for the most part it automatically works "out of the box" without much administrative overhead. The machine’s DNS entries in the NIC, must be ONLY configured to use the internal DNS servers that host the zone. Single label name zones are problematic, do not conform to the DNS RFC, and causes excessive internet traffic to the Root Servers when DNS tries to resolve a single label name query, such as querying for computername.domain – in such a query, the domain name is actually treated as a TLD.
DHCP Option 006 MUST only be the internal DNS server(s) you want to use, otherwise if using an ISP’s DNS or your router, expect undesired results. The Primary DNS Suffix on the machine MUST match the zone name in DNS. This is default and expected behavior, but if there are any DCs that have any problems, and the client resolved the SOA to that DC, it may not accept the update. The zone in DNS must NOT be a single lable name, such as "DOMAIN" instead of the required minimum of two hierarchal levels such as domain.com, domain.local, domain.me, domain.you, etc.
There are a few other settings that must be correct on each client as well.
Here's a Power Shell script that lets you easily test for multiple different problem scenarios. Ensure dynamic updates are enabled on the DNS zone This is less likely to be the problem because all clients would not be working is the dynamic updates setting on the DNS zone. If set to Secure, you may begin to see more instances like the ones we'll be talking about in #4 below. Check permissions on the dns Node AD object This problem in particular was extremely hard for us to track down on one occasion.
Quoted by Joseph Davies, MSFT: "IPv6 is a mandatory part of the Windows operating system and it is enabled and included in standard Windows service and application testing during the operating system development process.