May
19

Server GUID DNS name could not be resolved to an IP address

Server GUID DNS name could not be resolved to an IP address

If you get this error on your DC during dcdiag.exe tests or in any other way, there is a good chance that your DNS infrastructure is not working properly. In order to correct this issue, you can run the dcdiag.exe with a switch of /fix. Dcdiag is part of support tools or you can download it from Microsoft’s support website. On a command prompt from a DC, browse to the local of the dcdiag.exe folder, and enter dcdiag.exe /fix to correct this error. After this is complet, restart the netlogon service and flush DNS by entering ipconfig /flushdns and ipconfig /registerdns to complete this step. I haven’t gone step by step on this knowledge base under the assumption that the people who are reading this article will be very technical.

After these steps are completed, above error or adding other domain controllers to the domain should go away. Please refer to my earlier article about dcdiag for the tests you can run with this tool.

Speak Your Mind

*

© tecmaze.com . The content is copyrighted to tecmaze.com and may not be reproduced on other websites