DCDIAG detects error

  • Thread starter Thread starter Simon
  • Start date Start date
S

Simon

I have an active directory domain controller.
I checked the domain controller by DCDIAG.
DCDIAG detects an error as follows;

Server1'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 (xxxxx-xxxx-xxxxx-xxxxx._msdcs.domain1.local)
couldn't be resolved, the server name(server1.domain1.local) resolved to the
IP address (192.168.0.10) and was pinable.

There is no zone named _msdcs.domain1.local in the DNS.
Perhaps it is the reason of the error.

Any ideas or related technotes would be appreciated.

Simon
 
In
Simon said:
I have an active directory domain controller.
I checked the domain controller by DCDIAG.
DCDIAG detects an error as follows;

Server1'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
(xxxxx-xxxx-xxxxx-xxxxx._msdcs.domain1.local) couldn't be
resolved, the server name(server1.domain1.local) resolved
to the IP address (192.168.0.10) and was pinable.

There is no zone named _msdcs.domain1.local in the DNS.
Perhaps it is the reason of the error.

Any ideas or related technotes would be appreciated.

Simon
Click to expand...

In Windows 2000 the _msdcs is in a subfolder in the domain1.local zone.
If the sufolder is not being created, it could be any one or more reasons.
1. You're not using the DC's address for DNS (do not use your ISP's DNS in
any position of any domain member or DC).
2. You've got a disjointed namespace.
3. You're not allowing dynamic updates on the zone.

If you're not sure about a disjointed namespace post these three items:
ipconfig /all
AD Domain name from AD Users & Computers
List of Forward lookup zones in DNS
 
Thanks helpful advice!

There was ISP's DNS in the server's LAN connection at first.
I did not reboot the server after correcting the address.
After rebooting, the _msdcs has been created in a subfolder in the
domain1.local zone and DCDIAG passed it.

Simon
 
In
Simon said:
Thanks helpful advice!

There was ISP's DNS in the server's LAN connection at
first.
I did not reboot the server after correcting the address.
After rebooting, the _msdcs has been created in a
subfolder in the domain1.local zone and DCDIAG passed it.

Simon
Click to expand...

Good deal, keep in mind this goes for all members of an AD Domain, no ISP's
DNS allow on any interface in any position. This goes for dial up
interfaces, too.
 
Back
Top