We help IT Professionals succeed at work.

Unable to start DNS service on SBS 2003.

Last Modified: 2013-11-05
Unable to start Microsoft DNS Service on server1. Error 1053: The service did not respond to the start or control request in a timely fashion. - That is all I get when I try to start the DNS service.

This is SBS2003.

I have been having random things happening over the past two days. For example:
Network drives randomly dissappearing
Email working for some and not others
Outgoing email working but incoming not

Any help would be greatly appreciated.
Watch Question


I rebooted the server and looked in the events. This was listed there about 20 times during the reboot:

The dynamic registration of the DNS record '_ldap._tcp.pdc._msdcs.glenn-davis.com. 600 IN SRV 0 100 389 server1.glenn-davis.com.' failed on the following DNS server:  

DNS server IP address:  
Returned Response Code (RCODE): 5
Returned Status Code: 9017  

For computers and users to locate this domain controller, this record must be registered in DNS.  

Determine what might have caused this failure, resolve the problem, and initiate registration of the DNS records by the domain controller. To determine what might have caused this failure, run DCDiag.exe. You can find this program on the Windows Server 2003 installation CD in Support\Tools\support.cab. To learn more about  DCDiag.exe, see Help and Support Center. To initiate registration of the DNS records by  this domain controller, run 'nltest.exe /dsregdns' from the command prompt on the domain  controller or restart Net Logon service. Nltest.exe is available in the Microsoft Windows  Server Resource Kit CD.
  Or, you can manually add this record to DNS, but it is not recommended.  

Error Value: DNS bad key.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

While this could be a serious Active Directory problem, it might also be caused by some basic issues.  Have you checked the following -

1) Make sure that your DNS server is pointing to itself or another valid internal Active Directory DNS server on your network.  It should not be pointed to a DNS server on the Internet for resolution.
2) How good is your virus protection?  The service failure combined with disappearing network drives is classic for several older viruses.
3) It is possible that a DNS system file is corrupt.  Whenever you see a 1053 error, it's basically Windows way of saying, "I don't have a clue as to what just happened."  The internal server error is kind of a catch all for failing services.  You might try running a repair on the server files or if you have another server with the exact same version and patch levels, you could copy any DNS related files.

If all of these fail, I'd start to be suspecious of Active Directory corruption.

Hope this helps.
This one is on us!
(Get your first solution completely free - no credit card required)
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.