Good morning Tech's, I am having a weird intermitten problem with our DC. This box is Windows 2003 Standard SP2, holds our DNS, DHCP, AD, Print Server.
It seems that the DNS service is crashing at least once every 2 days. I am not 100% sure if its the DNS or the AD that is crashing. Seems like they work hand-and-hand.
I check the event logs and everytime it crashes we get the following errors:
Error 7053 (DNS)
Description: The DNS server sendto() funtion failed. the event data contains the error.
Error 4013 (DNS)
Description: The DNS server was unable to open the Active Directory. This DNS server is configured to use directory service information and can not oerpate without access to the directory. The DNS server will wait for the directory to start. If the DNS server is started but the appropriate 3even has not been logged, then the DNS server is still waiting for the directory to start.
I do not know if this has anything to do with the issue above but we switched Internet Providers. I called WHOIS on Tuesday and gave authority to our new ISP to handle our DNS. We planned on doing the switch over on Thursday so we gave WHOIS a few days notice for the DNS entries can properagte on the internet before the actual switch-over. The DNS crashed on Wed, the only change we made was on Tuesday but this change was made on the ISP side not on our internal network. I do not know if having the ISP in a way doing our DNS will screw with our internal DNS server.
Please help, your idea's are greatly appricated.
It seems that the DNS service is crashing at least once every 2 days. I am not 100% sure if its the DNS or the AD that is crashing. Seems like they work hand-and-hand.
I check the event logs and everytime it crashes we get the following errors:
Error 7053 (DNS)
Description: The DNS server sendto() funtion failed. the event data contains the error.
Error 4013 (DNS)
Description: The DNS server was unable to open the Active Directory. This DNS server is configured to use directory service information and can not oerpate without access to the directory. The DNS server will wait for the directory to start. If the DNS server is started but the appropriate 3even has not been logged, then the DNS server is still waiting for the directory to start.
I do not know if this has anything to do with the issue above but we switched Internet Providers. I called WHOIS on Tuesday and gave authority to our new ISP to handle our DNS. We planned on doing the switch over on Thursday so we gave WHOIS a few days notice for the DNS entries can properagte on the internet before the actual switch-over. The DNS crashed on Wed, the only change we made was on Tuesday but this change was made on the ISP side not on our internal network. I do not know if having the ISP in a way doing our DNS will screw with our internal DNS server.
Please help, your idea's are greatly appricated.