DNS stops with no reason Server 2008

DNS has stopped on my server a few times now. There are no meaningful errors so I don't know where to start.
Can anyone help?
HKFueyAsked:
Who is Participating?
 
HKFueyAuthor Commented:
OK, we applied this patch: -
http://support.microsoft.com/kb/979711
And the problem has gone away!
0
 
Dan ArseneauCommented:
On a Domain Controller or standalone?  If on a DC, run DCDIAG.  Many zones?
0
 
HKFueyAuthor Commented:
Yes it is a DC
DCDIAG /test:dns result =domain.com passed test DNS
0
On-Demand: Securing Your Wi-Fi for Summer Travel

Traveling this summer?Check out our on-demand webinar to learn about the importance of Wi-Fi security and 3 easy measures you can start taking immediately to protect your private data while using public Wi-Fi. Follow us today to learn more!

 
Dan ArseneauCommented:
How many zones?  Are you able to add new AD Integrated Zones without issues?
0
 
HKFueyAuthor Commented:
I think we only have one zone with 2 DC's both running DNS
0
 
GeodashCommented:
Change the service account running the DNS service to a different account and see if it still happens. The local service account can cause this on occasion.
0
 
HKFueyAuthor Commented:
That's interesting, I did try to change to Administrator but got error 1297 "A privelige that the service requires to function properly does not exist in the account information"
0
 
GeodashCommented:
Create a new test domain admin account (you can delete it after the test), name it accordingly (I name all of my service accounts like this - "svc.dns" so I can keep track of what accounts do with a simple LDAP query). Try using the credentials of the new account and see if the service starts.
0
 
HKFueyAuthor Commented:
I still get the same error with a dom admin account.
Going home for the weekend now, this will have to wait until Monday!!
0
 
WORKS2011Austin Tech CompanyCommented:
Have you checked other services dependent on DNS (see list below) any behavioral or entries in the log files? :
- Active Directory Domain Services
- Ancillary Function Driver for Winsock
- Remote Procedure Call (RPC)
- TCP/IP Protocol Driver

Are the "Recovery" options set to the following:
- First failure: Restart the service
- Second failure: Restart the service
- Subsequent failures: Take No Action
0
 
WORKS2011Austin Tech CompanyCommented:
DNS relies heavy on the NIC, could be a place to start. Most servers have two could switch to another NIC.
0
 
HKFueyAuthor Commented:
MS Patch appears to have solved!
0
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.