After Renaming Domain (RENDOM) there is a DNS issue.
Posted on 2014-09-18
Background: Set up a new server, new forest, new domain. It is the only server in the network/domain/forest.
I used the company's registered name: mycompany.com as the name of the domain. Bad move :( The company's web site is hosted on a remote hosting site (OK - I just redirect to the remote site). However, internal to the code of the website are all the links which reference mycompany.com/directory/file. So, no problem for remote users - but for the internal LAN users, everytime they would go to their own web site, it would not work properly. DNS on my new server would point to the inhouse server (which does NOT have any of these files).
Attempted Solution: Used RENDOM and ran through the process to rename the domain from mycompany.com to mycompany.local. Process worked and problem appeared to be solved.
Problem: However, when I ran DCDIAG it claims that this server fails the Connectivity test. Specifically, it says that the host: <GUID>._msdcs.mycompany.local could not be resolved to an IP address. When I look in the DNS tables, I see the mycompany.local in the Forward Lookup Zone. (Note: I deleted the mycompany.com which was previously there). However, in the mycompany.local zone, I see lots of references to mycompany.COM -- as if there are still buried references to the old domain name.
Question: How can I fix and/or cleanup DNS so that DCDIAG is happy? Are these references to mycompany.com in the mycompany.local lookup zone OK? TIA!!!