My 2008 R2 Domain Controller has no PTR record for itself
Hello experts,
Just came across an odd situation where one of my Windows 2008 R2 domain controllers does not have a PTR record in the Reverse Lookup Zone of my Active Directory integrated DNS.
I noticed this by doing an nslookup from my workstation. Since my primary DNS is the server I'm referring to above, the nslookup window starts with "Default Server: UNKOWN" and the IP address of the server below it.
All DNS resolution and network functionality is fine. I'm not sure if this existed for a while or whether it has to do with the fact that I just did some Windows Updates on just this one DC and rebooted it.
Will the PTR record come back on its own? Will I cause any problems by simply doing a "ipconfig /registerdns" command on the box. The TCP/IP properties on the DNS tab have the "register this connection in DNS" option selected.
Please provide feedback - thanks! I'd like to correct this the right way (and understand what happened here).
Just came across an odd situation where one of my Windows 2008 R2 domain controllers does not have a PTR record in the Reverse Lookup Zone of my Active Directory integrated DNS.
I noticed this by doing an nslookup from my workstation. Since my primary DNS is the server I'm referring to above, the nslookup window starts with "Default Server: UNKOWN" and the IP address of the server below it.
All DNS resolution and network functionality is fine. I'm not sure if this existed for a while or whether it has to do with the fact that I just did some Windows Updates on just this one DC and rebooted it.
Will the PTR record come back on its own? Will I cause any problems by simply doing a "ipconfig /registerdns" command on the box. The TCP/IP properties on the DNS tab have the "register this connection in DNS" option selected.
Please provide feedback - thanks! I'd like to correct this the right way (and understand what happened here).
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This worked in our simulated lab environment without issue so we plan on putting in production as well. Thanks for your assistance.
DNS registration of DC records should occur under any of the following conditions:
You restart the server(reboot)
You restart the netlogon service
These two options will impact on your server;
reboot - server unavailable.
restart netlogon - no user authentication from that server until the service restarts.
The following commans should not impact your server or clients.
You run ipconfig /registerdns
You run dnscmd /dsregdns
You can also add the record manually if desired.