Discussion Locked

Need DNS error help

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have three Win2K servers all as DC's I have been getting errors about syncing and I used the dsnlint program and recived the folloing error
"CNAME records for forest GUIDs missing on server:
GUID: 49450dba-8542-476b-816f-2bf531253536._msdcs.meelift.com
DC: ELMO"

How can I correct this? Can I try to Manually add this? On a second point these all Have Active Directory on them and they all have the same server listed as primary DNS, I was told that each server should have it's own IP address listed as Primary.

6 replies

by cul8rm8e

If you have DNS running on all DC`s then you should register its own IP address as primary DNS server if these are configured as child domains!

If thes DC`s are running as secondary DC`s of the same domain and your PDC has DNS running Active Directory Integrated zones and the DNS service is only running on your PDC make sure you have host records under your zones for your other 2 DC`s and allow dynamic updates under the properties of this zone.

by dennisbv

I have DNS running on all three servers and Now I have each server with its own Ip adderees as it's primary DNS. I have the same zone on all three and it is set allow zone transfers or updates from each other.
I rated this answer as not helpingbecause I am not sure of your answer.

by magetower

If I have read your information correctly you have three AD DCs all running DNS using only one DNS zone.

For this to work the server that was initially configured to host DNS should be the authoritative (or master) server for the zone. All other DNS servers should be considered secondary for the zone. (some things change if you have opted to run with integrated DNS)

What may be occuring is that the servers have not correctly registered with the master DNS server.

In the DNS configuration make sure that whichever one was the inital DNS is indicated as the master for the zone and that the other two servers are indicated as secondary. The DNS configuration on the other two servers should indicate that they are secondary servers to the master.

If all of this is correct then make sure the settings for the zone on the master is configured to allow dynamic updating.

(NOTE:One issue to look out for here is that Microsoft DNS does not automatically make a reverse lookup zone when the primary forward zone is created. If you do not see a reverse lookup zone for the IP range of your network then you need to create one and make sure it is also set for dynamic updating keeping in mind which is master and which are secondary servers.)

If every thing looks to be in place then you will need to force the servers to register with the DNS. [its suppose to be automatic but I've found it doesn't always work on servers]

You do this by entering the following in a command window on each server.

IPCONFIG /REGISTERDNS

Make sure to do this on the master server first.

You can tell if it worked if you see entries in the reverse zone appear that look like the one in your error message (after GUID:). If you don't see this within a few minutes then reboot the server.

by magetower

Without the entries in the reverse zone the sync process will not know where the servers are (thus the errors).

Sounds confusing but without knowing your exact setup its all I can do for now.

Hope this helps...

This discussion is closed to new replies.