Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Problem with DCDiag DNS server

1 view
Skip to first unread message

timg

unread,
Jun 2, 2004, 1:13:20 PM6/2/04
to
I ran DCDiag as a preparation for installing an Exchange server. The
'Connectivity" test failed with the message "The host <GUID>._msdcs.<NETBIOS
NAME>.<domainname>.com could not be resolved to an IP address."

I wonder if the problem is that our internal DNS server which this test was
meant to verify is not the authoritative DNS server for the domain. I
created an internal DNS server but the authoritative DNS server for our
domain is our ISP. Of course our ISP does not know anything about our
internal machines.

All other DCDiag tests succeed and NetDiag runs all tests just fine. Any
thoughts?

Thanx!


Ace Fekay [MVP]

unread,
Jun 4, 2004, 2:29:05 PM6/4/04
to
In news:10bs2qn...@corp.supernews.com,
timg <t...@deltacompsys.com> posted their thoughts, then I offered mine


Usually you'll get this if you are NOT using your internal DNS server. Make
sure that any references to any external DNS IP address (such as your ISP's_
are removed, flush your local cache and the DNS cache, and re-run the test.

If that doesn't work, post an ipconfig /all of the machine and let us know
what the AD DNS Domain name should be.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================


0 new messages