DCDIAG error on AD Controller

I noticed some 1864 errors regarding NTDS replication on our main AD
controller. When I run DCDIAG, under the connectivity tests, it says that
the GUID DC name does not resolve to an IP address, but the FQDN does
resolve to an IP Address. Then, it skips some tests because it is not
responding to dns requests. How can I resolve this?

In news:uWL8$(E-Mail Removed),
BG <(E-Mail Removed)> asked for help and I offered my suggestions below:
> I noticed some 1864 errors regarding NTDS replication on our main AD
> controller. When I run DCDIAG, under the connectivity tests, it
> says that the GUID DC name does not resolve to an IP address, but the
> FQDN does resolve to an IP Address. Then, it skips some tests
> because it is not responding to dns requests. How can I resolve this?

Sounds like your SRV records are either incorrect or non-existant. Do the
SRV folders show up under your zone?

If they do not, there are a number of rules required to be set for this to
work automatically. To better assist, please post this info to better assist
to eliminate guess work:

1. Unedited ipconfig /all
2. Exact spelling of the zone name in DNS and whether updates are set to
allow.
3. Exactg spelling of the AD DNS domain name

Thanks!

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
--
=================================