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.Visual Domain Routing Tool You can also ping and trace route your domain locally from your Windows/Mac command prompt to verify what IP you are actually seeing.If the ping and traceroute test show your server with us in the outcome, you know the DNS is propagated. You can try speeding up the propagation time by having your TTL set to a lower number (not recommended). We set the default TTL to 14400 (4 hours); however the network that you are using to access the internet may update at a slower rate.
When DDNS is working properly it's wonderful, but when it fails it can sometimes turn into a major pain to troubleshoot.
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.
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.
When you make a DNS change, it takes time for the changes to take effect. It is the time it takes for the domain DNS to refresh the cache on the network.