Server 2016 r2 dns not updating
On the DNS tab enable DNS dynamic updates and set to "Always dynamically update..." Also enable Dynamic Update for clients that do not request updates.1a) Even if these are enabled, you might need to make sure the DHCP server has permissions to update DNS records. 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.The following list illustrates a typical example of how a private DNS update leaks out to the global Internet. The DHCP client first sends a query to its local domain name server (LDNS) and asks for the authoritative server for the zone of its domain name (step 3).Once the DHCP client receives a response (step 4), it sends the update to the indicated server (step 5).
3) If the issue is that your reverse zones are mismatched between domain controllers (meaning a host was able to register with one of the DCs, but the registration did not get replicated to the others) it could mean the zones themselves aren't replicating between domain controllers.
The DHCP server in this case is NOT a windows server. 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.
I guess that the forward lookup records are created by the host, but the reverse records are created by the DHCP server?
It might be easier to drop your scope lease time really low, then delete all the dynamic DNS records and let them get re-created.
If you're waiting on DNS scavenging, there's no fast way to do it.