NETDIAG and DCDIAG Fails

[Gops]

I am unable to get through this issue. I have enclosed
the"NETDIAG" and DCDIAG results. Someone please suggest me
step by step how to resolve this issue.
------------------------------
C:\NETDIAG

DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative
DNS server for the name 'servername.DOMAINAME.'.
[RCODE_SERVER_FAILURE]
The name 'servername.DOMAINAME.' may not be
registered in DNS.
[WARNING] The DNS entries for this DC are not
registered correctly on DNS server '192.
168.34.8'. Please wait for 30 minutes for DNS server
replication.
[FATAL] No DNS servers have the DNS records for this
DC registered.

When I run DCDIAG test it fails. The out put is enclosed
below. (In the TCP/IP configuration the DNS entry is the
server's IP address).

C:\>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\SERVERNAME
Starting test: Connectivity 353c8b1b-525e-4cca-813e-
a2db0ead48cc._msdcs.DOMAIN-NAME'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
(353c8b1b-525e-4cca-813e-a2db0ead48cc._msdcs.DOMAIN-NAME)
couldn't be resolved, the server name (servername.DOMAIN-
NAME) resolved to the IP address (192.168.34.18) and was
pingable. Check that the IP address is registered
correctly with the DNS server.
......................... SERVERNAME failed test
Connectivity
------------------------------

 

[Tim Hines [MSFT]]

Based on the errors you have DNS problems. If you configure dns correctly
then that should resolve those errors. Make sure that you have created a
DNS zone for your domain on your DNS server and make sure that it allows
dynamic updates. Point your DCs to that DNS server for DNS resolution.
Make sure that the DCs TCP/IP settings are configured to register their
information in DNS. Once these steps have been taken you should run
ipconfig /registerdns and restart netlogon on the DCs. This should force
the DCs to register their IP address and SRV records in the DNS zone. Open
up the DNS console to verify that you have the new records there. You should
also see for folders (_mscdcs, _tcp, _udp and _sites.) . Try running
netdiag and dcdiag again after completing these steps.

--
--
Tim Hines, MCSE, MCSA
Windows 2000 Directory Services

=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Ace Fekay [MVP]]

In Gops <[email protected]> posted their thoughts, then I
offered mine

[WARNING] Cannot find a primary authoritative
DNS server for the name 'servername.DOMAINAME.'.
[RCODE_SERVER_FAILURE]
The name 'servername.DOMAINAME.' may not be
registered in DNS.
[WARNING] The DNS entries for this DC are not

<snip>

To add to what Tim mentions, and to continue on from your previous
post/thread, here's a reprint of what I posted in your other thread so as to
make sure you don't miss it. Awaiting your response...

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Gops, your whole issue is a single label name. Look at this article below.
But it's highly suggested to rebuild your domain with the proper name of
"domainname.com" instead of just "DOMAINNAME". THis is because AD is DNS
based. DNS is hierarchal. THere is no hierarchal structure with a single
label name such as what you have. A name of "domainname.com" does have a
hierarchy, it has a firstlevel domain name (com) and a second level domain
name (domainname), combined is domainname.com. DNS doesn't know how to
handle it, so therefore DNS will cause excessibe queries to the Root servers
on the Internet. Mirosoft stopped this excessive traffic with SP4, since
that was the right thing to do to calm down the excessive traffic to the ISC
Roots. The link below shows how to bypass that restricition. You need to do
this on all your machines. However, this may or may not guarantee that GPOs
will work properly, since when the GetGpoList function runs, it finds the
GPOs by connecting to a UNC such as:
\\domainname.com\sysvol\domainname.com\policies.
if it were a single label name, it connects to:
\\domainname\sysvol\domainname\policies
and will treat it as a computer name instead of the domain name and may
fail. Same with DFS.

300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names [needs the domain.com name and cannot be
just --domain--]:
http://support.microsoft.com/?id=300684

Good luck.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

--
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. --
=================================