We put a new DC in one of my sites this afternoon. This is a Win2000
DC, in a child domain. My guys added it to the domain, and made it a
domain controller. THEN they decided to put DNS on it ...
And now I am getting DNS failures, when running DCDIAG.
Testing server: MajorSystems\MJRSWDC003
Starting test: Connectivity
MJRSWDC003's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(064ff8f1-0843-4833-bc82-2c41e08a97f0._msdcs.ads.pha.phila.gov)
couldn't be
resolved, the server name (MJRSWDC003) resolved to the IP
address (10.64.62.241
and was pingable. Check that the IP address is registered
correctly with the
DNS server.
......................... MJRSWDC003 failed test Connectivity
The weird thing? that record that couldn't be found is not the domain
of this DC; that indicates the parent domain ...
dnslint says:
CNAME: 064ff8f1-0843-4833-bc82-2c41e08a97f0._msdcs.ads.pha.phila.gov
Alias: mjrswdc003
Glue: Unknown
I can see where to add the CNAME in the DNS of the parent domain, but
have no clue how to add the GLUE record.
DCDIAG /FIX does nothing to resolve this. They've tried uninstalling
and re-installing the DNS service, to no avail.
<SIGH> A horrible for for AD for me ...
Anyone?
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
