DCDIAG detects an error.

[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

 

[ptwilliams]

Ensure that the DNS zone supports dynamic updates, and that the DHCP client
service is running on your DC (even though you're not running DHCP) and
restart the netlogon service. Wait a few minutes and run the test again...

--

Paul Williams
_________________________________________
http://www.msresource.net


Join us in our new forums!
http://forums.msresource.net
_________________________________________


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

 

[Cary Shultz [A.D. MVP]]

Good call, Paul.

I would also want to verify that the four sub folders are in the
'domain.local' FLZ and that each is populated correctly.

I would really check to make sure that the alias for the DC in question is
correct. Meaning, that someone did not manually change it. If he has the
Support Tools installed he could run repadmin /showreps and repadmin
/showconn to make sure ( IIRC ).

Cary

 

[Simon]

Thanks for your advice.
The DC had ISP's DNS address in the LAN setting.
I replaced the address with DC's one.
After rebooting, the _msdcs.domain1.local was created.

Simon