Windows dns reverse lookup not updating
riginally posted this in 4/2006, and updated throughout the years, but I still get questions from time to time asking why updates are not working, especially PTR.
Well, I thought it’s time for an update and to just offer a summary in the beginning, because in this day and age, no one wants to read!
You must enable DNS dynamic updates and choose the option for "Always dynamically update DNS A and PTR records, and to Discard A and PTR records when the lease is deleted.
Image of the DNS tab Another issue that we found out is if the DNS zone (both) is set to Secure only.
Edit: According to the article linked by The Cleaner below, the GPO I mentioned in my comment will not do what you want (yeah MS and closed-source software).
Have them set to be secure and non-secure on both the forward and reverse lookup zones.Visit Stack Exchange I've stumbled upon a strange behaviour with Windows machines, which seems to be fairly consistent between all Windows versions from Vista/2008 to 8.1/2012 R2; it doesn't happen instead when using Windows XP or Windows Server 2003.The problem is this: when the network adapter is configured for DHCP and the DHCP server doesn't register DNS records on behalf of its clients (because it can't, or because it's not configured to do so), then in the TCP/IP settings of the network interface: As much as it may appear strange, this is the only solution to ensure Windows will register both the A and the PTR records for a DHCP network connection; otherwise, it will only register the A record.You can read more about this in my DNS Best Practices guide.
These steps are very similar across other all server versions server versions (2008, 2012).
In this tutorial, I’ll show you step by step instructions for configuring reverse DNS lookup zones and PTR Records on Windows Server 2016.