DNS Problems on SBS 2003 Server


I have a SBS 2003 server which seems to be causing problems with reverse lookups, a recursive test fails and as a result of the issues with the dns I am not able to connect new computers to the network because server.domain.local does not resolve to the servers IP address.

I have checked the DNS server and it does have a reverse lookup zone which appears correctly populated.

Any ideas how this can be fixed?
Who is Participating?
netcmhConnect With a Mentor Commented:
I believe so. I wouldn't want different errors compounding the issue.
Does your SBS server have all the roles assigned to it?

Try the following:
Stop & start the DNS service

Try ipconfig /flushdns

Stop & start the NETLogon service

ipconfig /registerdns

what does dcdiag show?
Tahir2008Author Commented:
I have made the changes requested but the issue remains:

C:\Documents and Settings\Administrator>ipconfig /flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

C:\Documents and Settings\Administrator>ipconfig /registerdns

Windows IP Configuration

Registration of the DNS resource records for all adapters of this computer has b
een initiated. Any errors will be reported in the Event Viewer in 15 minutes..

C:\Documents and Settings\Administrator>nslookup server.domain.local
Server:  server.domain.local

*** server.domain.local can't find server.domain.local: Non-existent domain

C:\Documents and Settings\Administrator>
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tahir2008Author Commented:
On another note, this is listed in the DNS under event viewer which could be part of the problem:

The DNS server was unable to complete directory service enumeration of zone domain.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.
Radhakrishnan RSenior Technical LeadCommented:
Is the reverse lookup zone is Active directory integrated? if not, try to change this and see it works fine.

Perform a dcdiag and see any DNS related error appears?
Tahir2008Author Commented:
Everything should be AD integrated as its part of the default setup of SBS 2003. Can you tell me the best process to perform a dcdiag?

It could be that your AD is corrupt. What's the output of the dcdiag command?
on your DC, run Dcdiag /fix output
Tahir2008Author Commented:
DCDiag shows the following:

Starting test: Services
      IsmServ Service is stopped on [SERVER]
   ......................... SERVER failed test Services

Starting test: frsevent
   There are warning or error events within the last 24 hours after the
   SYSVOL has been shared.  Failing SYSVOL replication problems may cause
   Group Policy problems.
   ......................... SERVER failed test frsevent

Nothing else is listed.
Radhakrishnan RConnect With a Mentor Senior Technical LeadCommented:
I would sugegst, reboot the server and run the dcdiag again as it is missing lot of informations.
Tahir2008Author Commented:
I only posted the items which failed from the report.
Radhakrishnan RSenior Technical LeadCommented:
Is there any errors is File replication event logs?
Tahir2008Author Commented:
This is what is displayed:

The File Replication Service has detected that the replica set "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)" is in JRNL_WRAP_ERROR.
 Replica set name is    : "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
 Replica root path is   : "c:\windows\sysvol\domain"
 Replica root volume is : "\\.\C:"
 A Replica set hits JRNL_WRAP_ERROR when the record that it is trying to read from the NTFS USN journal is not found.  This can occur because of one of the following reasons.
 [1] Volume "\\.\C:" has been formatted.
 [2] The NTFS USN journal on volume "\\.\C:" has been deleted.
 [3] The NTFS USN journal on volume "\\.\C:" has been truncated. Chkdsk can truncate the journal if it finds corrupt entries at the end of the journal.
 [4] File Replication Service was not running on this computer for a long time.
 [5] File Replication Service could not keep up with the rate of Disk IO activity on "\\.\C:".
 Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state.
 [1] At the first poll, which will occur in 5 minutes, this computer will be deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service.
 [2] At the poll following the deletion this computer will be re-added to the replica set. The re-addition will trigger a full tree sync for the replica set.
WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the data unexpectedly unavailable if this error condition occurs again.
To change this registry parameter, run regedit.
Click on Start, Run and type regedit.
Click down the key path:
Double click on the value name
   "Enable Journal Wrap Automatic Restore"
and update the value.
If the value name is not present you may add it with the New->DWORD Value function under the Edit Menu item. Type the value name exactly as shown above.
Radhakrishnan RConnect With a Mentor Senior Technical LeadCommented:
I think you need to perform Burflag in order to get rid of the replication issue. How many DC's you have?

If you have more than 1 DC then follow the procedure http://adfordummiez.com/?p=61
Tahir2008Author Commented:
I dont know what this and there are only two servers. The SBS2003 server server which is the DC and another server which functions as a Sage 200 server.
I think the FRS service is in error. Please see this KB article http://support.microsoft.com/kb/290762. This might help you resolve the issue. You might have to do the authoritative restore mentioned in that link.
Tahir2008Author Commented:
The chkdsk also reported errors which it was not able to fix in read-only mode. My concern in allowing it to perform a full chkdsk is that it could break the box if the issue is serious as has occurred previously on desktop computers, would it better to fix the disk errors first before attempting a restore?
Tahir2008Author Commented:
Thanks a combination of the above responses assisted greatly and a chkdsk over the server in a test environment first resolved the issue, I then performed this on the live server and the issue is now resolved. After the chkdsk the DNS server is fully functional and responding to internal server requests.

Wonderful news. Good job getting it resolved. Thanks for the grade. Good luck.
Tahir2008Author Commented:
Seems the problem has not been fixed. Although the DNS is now working and resolving when attempting to add a computer to the domain I still receive the following message:

Note: This information is intended for a network administrator.  If you are not your network's administrator, notify the administrator that you received this information, which has been recorded in the file C:\windows\debug\dcdiag.txt.

The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "domain.local":

The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)

The query was for the SRV record for _ldap._tcp.dc._msdcs.domain.local

Common causes of this error include the following:

- The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at set intervals. This computer is configured to use DNS servers with the following IP addresses:

- One or more of the following zones do not include delegation to its child zone:

. (the root zone)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.