Reverse dns zone not updating
Even if you don’t have requirements for them I still recommend setting them up because they are extremely helpful when troubleshooting.You can read more about this in my DNS Best Practices guide.The only thing I had to do after this was, flush the dns entries on the clients with: ipconfig /flushdns After this they have poped up in my reverse lookup zone. The fix of adding the DHCP server to DNSupdateproxy group solved my issues. In this tutorial, I’ll show you step by step instructions for configuring reverse DNS lookup zones and PTR Records on Windows Server 2016.The forward DNS entries ("A" records) for windows machines on the domain are populated automatically.However, the reverse DNS entries ("PTR" Records) are not.If so, your DHCP server may not be configured to auto-register their IP with the DNS server.To check, right-click your DHCP scope and go to properties.
Visit Stack Exchange We use windows server 2003 for DNS on our network.
If your DHCP server is also a domain controller, then you are probably fine, if not, then you may want to see if the DHCP server is a member of the "Dns Update Proxy" group in AD.
Then check the Security tab on the Reverse Zone and make sure that group is authorized to create all child objects (DNS records) 2) If your statically-configured hosts are not updating the reverse zone, make sure their NICs are configured to register their IP in DNS (Windows hosts are enabled for this by default).
If there are missing entries, you likely have your DHCP missing one of two settings: This is required if you have DHCP installed on a Domain Controller.
It is an issue on Server 2000, 2003, 2008, 2008R2, Server 2012, Server 2012 R2 and will likely be an issue in the newer builds.