DNS Error message help required

[TechSupp]

Just checking back through the error logs and have discovered the following error messages for DNS Server in Event Viewer, happened in January and October but don't know why and each time there are the group of 5 messages together. Inbetween times just messages that the DNS Server has started. Should I be worried about this error?

 

The DNS server was unable to complete directory service enumeration of zone DOMAINNAME.local. This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empty) is "". The event data contains the error.

 

The DNS server was unable to complete directory service enumeration of zone 116.xx.xx.in-addr.arpa. This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empty) is "". The event data contains the error

 

The DNS server was unable to complete directory service enumeration of zone _msdcs.Domain Name.local. This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empty) is "". The event data contains the error.

 

The DNS server was unable to complete directory service enumeration of zone .. This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empty) is "". The event data contains the error.

 

The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error.

 

 

 

 

Now they means absoluetly nothing to me, can anyone enlighten me as to what the error is, what effect the error is having and how I should go about fixing it? (Writing in italics are my edits as they are our domain names and IP's)

 

Thanks

Edited December 18, 2009 by TechSupp

[DMcCoy]

does it happen during boot? Is there only one DC? Is the message repeated?

[TechSupp]

There is only one DC, it has shown in the logs twice this year, January and October and I'm sure the server has been rebooted inbetween those times (but may be mistaken so it could be at boot time, can't check that at the moment as all are on it ). The October and January instances of this error are the same 5 events in the event viewer all together.

[DMcCoy]

There is only one DC, it has shown in the logs twice this year, January and October and I'm sure the server has been rebooted inbetween those times (but may be mistaken so it could be at boot time, can't check that at the moment as all are on it ). The October and January instances of this error are the same 5 events in the event viewer all together.

 

If there is only one DC and it happens after a reboot then there is nothing to worry about, sometimes DNS will start before the AD services causing this error. If the zones are all present in the DNS management console then they have loaded correctly, although a little delayed after the initial boot.

[sparkeh]

I get this on reboot of my single server site too. And as DMcCoy says its down to DNS loading before AD.

Just check that DNS does load ok after boot and everything should be fine.

[powdarrmonkey]

It's a chicken and egg problem - with Active Directory integrated zones, both DNS and AD depend on each other. Active Directory depends more strongly on DNS than vice versa though, so Windows starts DNS services first.