Reverse lookup zone not updating
Can someone please help, we are running Windows 2003 DC (FSMO roles) and Windows 2008 DC (additional DC) AD Integrated DNS.
Thanks, Do you wonder if your IT business is truly profitable or if you should raise your prices?
For those who have tried, they probably noticed that none of the computers did dynamically register the reverse lookup (PTR) records in DNS.
So what need to be done for each Azure VMs to register their PTR record dynamically?
Once everything is cleaned then I might turn on scavenging.
Mike and Matt thank you for all your help, I will be going through list of active PC and deleting A and PTR records manually since DHCP is via firewall and after reading scavenging article that it might create more issues.
The setting with some additional info: Although the policy came through just fine, even after a reboot, my client was not registering his PTR record…
I also attached a VBScript version for those who would rather use VBScript then update all the Win2008R2 systems to Power Shell V3.
Update [27/06/2013]: new information regarding the topic: Windows 7 & Reverse Lookup DNS Registration [Update] In my current project we have an Active Directory domain where we use Windows DNS servers with domain integrated DNS zones.
Quite simple, the DNS Dynamic Registration setting under manual configuration of NIC properties in Azure are not persistent, so it must be automated.
The solution provided below is a suggested solution to automate the process using a Power Shell startup script in Active Directory Group Policy (GPO) Power Shell v3.0 is required for the script to complete work on Win2008R2.