Maybe these short youtubes help with configuration.
https://www.youtube.com/watch?v=yBVVGJ2Z4i0
https://www.youtube.com/watch?v=Tukvch2Qtuc
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We have an issue where the forward DNS zone will update each time a PC obtains a DHCP lease, but the respective PTR record on the reverse lookup fails to update even though the Update the pointer (PTR) record checkbox is marked for all machines. We also have a group policy in place to enable the registration of PTR Records and our settings in DHCP are set to always dynamically update dns records. We also have scavenging of dns records disabled.
Most of our machines obtain DNS via DHCP and I did find last week that the server options needed to be updated in our DHCP Utility (this had been previously missed), but even after fixing those, it appears the dynamic updates are still not working correctly. Our DNS settings on all the machines are pointing to the correct sources. Last month, we even had someone og through, using power automate, and uncheck and recheck the Update the pointer (PTR) record checkbox for all dns entries, and it updated the reverse dns entry that day when this issue was discovered, but those records have not update since, and it has led to at least one incorrect reverse dns resolution.
I will tell you that our current setup is as follows. We have two domain controllers, a primary and a secondary that replicate to each other. The secondary domain controller is in Azure Private Cloud and it connects to our on-premise domain controller via site-to-site VPN. Both are running Windows Server 2016 Datacenter x64.
Any thoughts? I have looked around and have not gotten anywhere. Thank you.
Maybe these short youtubes help with configuration.
https://www.youtube.com/watch?v=yBVVGJ2Z4i0
https://www.youtube.com/watch?v=Tukvch2Qtuc
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
Hello Jesse,
A similar issue that I used to have, has been solved when I start looking the network firewall (not the windows) between DHCP Server DNS and clients. The other thing that you need to check is, if the dhcp service user has enough rights to make changes on the DNS.
Also, you can check the following article:
https://learn.microsoft.com/en-us/answers/questions/701888/windows-dns-ptr-records-not-creating-via-dhcp.html
--please don't forget to upvote and Accept as answer if the reply is helpful--
BR,
I posted this issue on SpiceWorks as well, and steps 3-6 of this article solved it for me:
https://community.spiceworks.com/how_to/177637-how-to-fix-a-non-updating-dynamic-reverse-lookup-zone