Jesoba.com is launched, Click below image to access it

Jesoba.com is launched, Click below image to access it
Technology and Entertainment Blog

AD Connectivity Test failed because GUID DNS name could not be resolved

Title: AD Connectivity Test failed because GUID DNS name could not be resolved

Description:

The DC Diagnostic connectvity test failed because GUID DNS name could not be resolved. This can be caused if the zone is not dynamic or the zone doesn't exist. Multiple

DNS servers, but not replicated can also cause this issue.

Possible cause could be:
On DNS Server:
1) zone is not dynamic
2) zone doesn't exist

3) Multiple DNS servers, but not replicated (see other fixes too)
arrange secondary zone transfer from primary or other master Check the above for both the "domain zone" and the _MSDCS zone if it is separate (i.e., not a subdomain of the domain zone itself.)

On DC as a DNS "client":
1) NIC must point STRICTLY at the INTERNAL DNS servers
2) Remove any external (ISP etc) DNS server
3) If replication problem persists, set all DCs to ONE "favored" DNS server until replication is fixed -- inefficient but works fortemporary fix purposes

DC replication of AD and integrated DNS:

1) DCs are AD Integrated but not replicating so DNS is also not
replicating.

Keyword
: dns test failed

No comments:

Google+ Badge

About Author

My photo

I am Senior Server Expert and Professional Blogger.