Dhcp updating dns records great profile description for dating site
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!
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.
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.
If the client isn't sending the update, it's not getting to the server so server troubleshooting will be useless.
Likewise, if the server is receiving the update but the record is still not getting updated then it might be a dns Node object permission problem. If you need help, this Technet article is a great resource we'd recommend for understanding the entire workflow from client to server.
This can get complicated so if you suspect this is the case, we advise checking out this blog post entitled How to Fix Dynamic DNS Record Permissions Automagically. Temporarily enable DNS debug logging on your DNS server Enabling debug logging on your DNS server allows the server to begin generating a debug log of all dynamic update activity. We have a Power Shell script to ease the pain by displaying the content in a more user-friendly format.