Question : DCDIAG Connectivity failure

Hello,
I recently inherited a small network and when I run dcdiag on my DC I receive the error pasted below. The domain has been running fine for months and there are no apparent issues. Aside from the fact that when I try to add another DC to the domain I am having trouble.  The server is running an up to date installation of Win 2003. This server is the DNS server and points to itself. AD is also on this server and runs well. The network has 34 computers on it hasn't shown any major issues. There is an A record in DNS and the IP is reserved in DHCP. I'm sure more info would be needed but I'd appreciate any follow up questions to gather more info or any suggestions for a resolution.

Thank you,

Flynn

Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\SERVERNAME
Starting test: Connectivity
The host xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx._msdcs.SERVERNAME.local
could not be resolved to an
IP address.  Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx._msdcs.SERVERNAME.local) couldn't be resolved, the server name (SERVERNAME.local) resolved to the IP address (xxx.xxx.xxx.xxx) and was pingable.  Check that the IP address is registered correctly with the DNS server.
......................... SERVERNAME failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\SERVERNAME
Skipping all tests, because server SERVERNAME is not responding to directory service requests
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
........................ DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
 ......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
........................ Configuration passed test CheckSDRefDom
Running partition tests on : DOMAINNAME
Starting test: CrossRefValidation
......................... DOMAINNAME passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DOMAINNAME passed test CheckSDRefDom
Running enterprise tests on : DOMAINNAME.local
Starting test: Intersite
....................... DOMAINNAME.local passed test Intersite
Starting test: FsmoCheck
......................... DOMAINNAME.local passed test FsmoCheck

Answer : DCDIAG Connectivity failure

What I have always done to register the correct DNS records for the server is go to the command prompt and type:

IPconfig /flushDNS
IPconfig /registerDNS
Net Stop Netlogon
Net Start Netlogon

Then I would replicate those to the other server. However, those commands will only register the HOST A record for the server and the SVR record for the server. You mentioned that the CNAME records don't exist. CNAME records are like assigning an alias to the HOST A record.

A CNAME record maps an alias DNS name to a HOST A record.
Example:
If your HOST A record for your domain controller is
server.domain.name.gov
And you commonly refer to that record by,
myserver.gov
You can create an alias record or CNAME record for that function.
So, it may not be necessary to do this.

Sometimes CNAME records can be used to separate your DCs from your clients.
In this case you have a DNS name of:
servername.domain.name.gov
and clients on what looks like a different FQDN of:
domain.name.ship
A CNAME record can make the transition between the two.

CNAMES are pretty much an Alias to the Host A record. So they shouldn't be necessary for your domain.