DNS Problems - SBS2003 - TechRepublic
Question
March 26, 2009 at 06:36 AM
allan.kendall

DNS Problems – SBS2003

by allan.kendall . Updated 17 years, 3 months ago

Hello Everyone,

I am looking for some advice with problems that I have been having. My SBS 2003 event log is showing DNS errors.
Those errors where as follows.

1) The DNS Server was unable to complete directoy service enumeration of zone company.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 Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empy) is “”.

2) The DNS Server was unable to complete directoy service enumeration of zone 0.168.192.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 Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empy) is “”.

3) The DNS Server was unable to complete directoy 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 Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empy) is “”.

4) The DNS Server was unable to complete directoy service enumeration of zone _msdcs.company.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 Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empy) is “”.

5) The DNS server has encountered a critial error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is “”.

Prior to the above errors which surfaced today, I had only one error which was with reference to a Host Records A replciation issue. I have changed the server to listen to its own IP address only. It was listening to its own plus another IP address that related to a secondary NIC that is now disabled.

There are so many errors as listed above I really need help. To get a clearer picture about what those errors where I ran netdiag (failed to run) and dcdiag. The reports came back with a fair few points of information.

Active Directory from DNSLint Report:

DNSLint Report

System Date: Thu Mar 26 11:48:57 2009

Command run:

DNSLINT /ad 192.168.0.16 /s 192.168.0.21 /v

Root of Active Directory Forest:

company.local

Active Directory Forest Replication GUIDs Found:

DC: COMPANYDC01
GUID: 2dc32bc4-36d7-4eda-9eb8-707781b4e2ac

Total GUIDs found: 1

——————————————————————————–

The following 1 DNS servers were checked for records related to AD forest replication:

DNS server: User Specified DNS Server
IP Address: 192.168.0.21
UDP port 53 responding to queries: NO
TCP port 53 responding to queries: Not tested
Answering authoritatively for domain: Unknown

SOA record data from server:
Authoritative name server: Unknown
Hostmaster: Unknown
Zone serial number: Unknown
Zone expires in: Unknown
Refresh period: Unknown
Retry delay: Unknown
Default (minimum) TTL: Unknown

——————————————————————————–

Notes:
One or more DNS servers may not be authoritative for the domain
One or more DNS servers did not respond to UDP queries
One or more zone files may have expired
SOA record data was unavailable and/or missing on one or more DNS servers

——————————————————————————–

Legend: warning, error

DNSLint developed by Tim Rains

DCDIAG Report:
Domain Controller Diagnosis

Performaing initial setup:
Done Gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\COMPANYDC01
Starting test: Connectivity
COMPANYDC01’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 (xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx._msdcs.company.local) couldn’t be resolved, the servername (COMPANYDC01.company.local) resolved to the IP address (192.168.0.16) and was pingable. Check that the IP address is registered correctly with the DNS server.
…………………………COMPANYDC01 failed test connectivity.

Testing Server: Default-First-Site-Name\COMPANYDC01
Skipping all tests, because server COMPANYDC01 is not responding to directory service requests.

I get the general idea of whats gone wrong, I just really need the advice and help to put it all right. All your input is welcome and if I can suuply you with more details then let me know. COMPANYDC01 etc etc is what I have changed because of this being a public post on a forum.

Thanking you all in advance

Yan.

This discussion is locked

All Comments