DNS Server service stopped without any reason
-
Hi, I have a problem with my windows server 2003 Sp1 DNS service. The problem is the DNS service on windows usually stop whether I changed its setting to Automatic Start for DNS Server service. As network administrator, I didn't change any setting relating to DNS service after I have configure it correctly. From here, I would like to know whether some of you experience with any virus that could stop DNS from running? When its stop, my whole organization could not access to an internet for a while. So I have to enable it every time to solve the problem. My concern is sometime I need to travel away from my office and this problem occure, so there would be nobody could solve this problem. Thank in advance
-
Hi, I have a problem with my windows server 2003 Sp1 DNS service. The problem is the DNS service on windows usually stop whether I changed its setting to Automatic Start for DNS Server service. As network administrator, I didn't change any setting relating to DNS service after I have configure it correctly. From here, I would like to know whether some of you experience with any virus that could stop DNS from running? When its stop, my whole organization could not access to an internet for a while. So I have to enable it every time to solve the problem. My concern is sometime I need to travel away from my office and this problem occure, so there would be nobody could solve this problem. Thank in advance
You did read this one[^] in the daily CP newsletter, did you? I hope your problem is something else tho. :)
Luc Pattyn [Forum Guidelines] [My Articles]
Voting for dummies? No thanks. X|
-
Hi, I have a problem with my windows server 2003 Sp1 DNS service. The problem is the DNS service on windows usually stop whether I changed its setting to Automatic Start for DNS Server service. As network administrator, I didn't change any setting relating to DNS service after I have configure it correctly. From here, I would like to know whether some of you experience with any virus that could stop DNS from running? When its stop, my whole organization could not access to an internet for a while. So I have to enable it every time to solve the problem. My concern is sometime I need to travel away from my office and this problem occure, so there would be nobody could solve this problem. Thank in advance
I would update to Service Pack 2 first of all, there is always the chance that will solve the problem, plus probably better of at SP 2 anyway if at all possible. Are there any errors in the event logs related to the DNS service? Is all DNS name resolution on the network failing or just Internet related queries? I probably wouldn't point to a virus for this problem, although its tough to say from your description. Up to date virus signatures and a full scan are never a bad idea though. You may want to try reinstalling DNS if updating to SP 2 doesn't help. (If you only have one DNS server and you're using Active Directory you might want to look for a MS document on how they say to do this, if there is one.)
-
Hi, I have a problem with my windows server 2003 Sp1 DNS service. The problem is the DNS service on windows usually stop whether I changed its setting to Automatic Start for DNS Server service. As network administrator, I didn't change any setting relating to DNS service after I have configure it correctly. From here, I would like to know whether some of you experience with any virus that could stop DNS from running? When its stop, my whole organization could not access to an internet for a while. So I have to enable it every time to solve the problem. My concern is sometime I need to travel away from my office and this problem occure, so there would be nobody could solve this problem. Thank in advance
As a temporary solution, to allow you to leave your office, you could set the service to restart automatically. In the services console, doubleclick the dns-service (or rightclick and select Properties). In the properties window select the recovery tab and select your options on failure. You naturally need to address the issue why the service fails. But to help you with that we need more data, such as relevant entries in the event log. When you have fixed the problem. don't leave the setting on automatic restart. It might prevent you from finding out that you're having a problem. Atleast if you like me read the eventlog irregularily.
-
You did read this one[^] in the daily CP newsletter, did you? I hope your problem is something else tho. :)
Luc Pattyn [Forum Guidelines] [My Articles]
Voting for dummies? No thanks. X|
-
I would update to Service Pack 2 first of all, there is always the chance that will solve the problem, plus probably better of at SP 2 anyway if at all possible. Are there any errors in the event logs related to the DNS service? Is all DNS name resolution on the network failing or just Internet related queries? I probably wouldn't point to a virus for this problem, although its tough to say from your description. Up to date virus signatures and a full scan are never a bad idea though. You may want to try reinstalling DNS if updating to SP 2 doesn't help. (If you only have one DNS server and you're using Active Directory you might want to look for a MS document on how they say to do this, if there is one.)
requesttimedout wrote:
I would update to Service Pack 2 first of all, there is always the chance that will solve the problem, plus probably better of at SP 2 anyway if at all possible.
Thank you very much for your comment. I have run windows update on the server and found that its recommend to update to windows 2003 sp2. Currently this server is acting as domain controller and file server which share a document to all user in the organization. As I have discussed with my team, I not sure whether if I apply sp2, whether the the server could running properly or not (may be it could cause some problem with any device driver, or strict any security seeting) which could cause a trouble for user to access the resource on the server. If you have any experience with sp2 on windows 2003, please let me know whether it have any problem or not after you apply it.
requesttimedout wrote:
Are there any errors in the event logs related to the DNS service? Is all DNS name resolution on the network failing or just Internet related queries?
When I found that the DNS server service is stopped, around 70% of my client couldn't access to an internet. But each client I also configure with an alternative ISP DNS. I also have some problem with my router too which could make me difficult to find the problem. After I turn off the router for 10 mintue and restart the DNS services, every body could access the internet again. I have check an event viewer to find the cause of the problem but I didn't found any entry that could cause DNS server service to stop. But I found the below entry that is related to the DNS server service:
Event Type: Error Event Source: DNS Event Category: None Event ID: 4007 Date: 18-Jul-08 Time: 8:10:52 AM User: N/A Computer: SERVER Description: The DNS server was unable to open zone _msdcs.pr.org.kh in the Active Directory from the application directory partition ForestDnsZones.pr.org.kh. This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and reload the zone. The event data is the error code. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 0d 00 00 00 ....andEvent Type: Error Event Source: DNS Event Category: None Event ID: 4007 Da -
As a temporary solution, to allow you to leave your office, you could set the service to restart automatically. In the services console, doubleclick the dns-service (or rightclick and select Properties). In the properties window select the recovery tab and select your options on failure. You naturally need to address the issue why the service fails. But to help you with that we need more data, such as relevant entries in the event log. When you have fixed the problem. don't leave the setting on automatic restart. It might prevent you from finding out that you're having a problem. Atleast if you like me read the eventlog irregularily.
Jörgen Andersson wrote:
As a temporary solution, to allow you to leave your office, you could set the service to restart automatically. In the services console, doubleclick the dns-service (or rightclick and select Properties). In the properties window select the recovery tab and select your options on failure.
Thank you very much for your comment. That is one solution that could help me to temporary solve it.
Jörgen Andersson wrote:
You naturally need to address the issue why the service fails. But to help you with that we need more data, such as relevant entries in the event log.
That was my biggest challenge. I have checked in the event viewer and there is no entry that show me the reason why DNS server service is stopped. But I found the following error related to DNS server service that could give you some idea:
Event Type: Error Event Source: DNS Event Category: None Event ID: 4007 Date: 18-Jul-08 Time: 8:10:52 AM User: N/A Computer: SERVER Description: The DNS server was unable to open zone _msdcs.pr.org.kh in the Active Directory from the application directory partition ForestDnsZones.pr.org.kh. This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and reload the zone. The event data is the error code. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 0d 00 00 00 ....andEvent Type: Error Event Source: DNS Event Category: None Event ID: 4007 Date: 18-Jul-08 Time: 4:40:01 PM User: N/A Computer: SERVER Description: The DNS server was unable to open zone pr.org.kh in the Active Directory from the application directory partition DomainDnsZones.pr.org.kh. This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and reload the zone. The event data is the error code. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 0d 00 00 00 ....Please let me know if you have any solution with the above error escription. Thank in advance!!! -
requesttimedout wrote:
I would update to Service Pack 2 first of all, there is always the chance that will solve the problem, plus probably better of at SP 2 anyway if at all possible.
Thank you very much for your comment. I have run windows update on the server and found that its recommend to update to windows 2003 sp2. Currently this server is acting as domain controller and file server which share a document to all user in the organization. As I have discussed with my team, I not sure whether if I apply sp2, whether the the server could running properly or not (may be it could cause some problem with any device driver, or strict any security seeting) which could cause a trouble for user to access the resource on the server. If you have any experience with sp2 on windows 2003, please let me know whether it have any problem or not after you apply it.
requesttimedout wrote:
Are there any errors in the event logs related to the DNS service? Is all DNS name resolution on the network failing or just Internet related queries?
When I found that the DNS server service is stopped, around 70% of my client couldn't access to an internet. But each client I also configure with an alternative ISP DNS. I also have some problem with my router too which could make me difficult to find the problem. After I turn off the router for 10 mintue and restart the DNS services, every body could access the internet again. I have check an event viewer to find the cause of the problem but I didn't found any entry that could cause DNS server service to stop. But I found the below entry that is related to the DNS server service:
Event Type: Error Event Source: DNS Event Category: None Event ID: 4007 Date: 18-Jul-08 Time: 8:10:52 AM User: N/A Computer: SERVER Description: The DNS server was unable to open zone _msdcs.pr.org.kh in the Active Directory from the application directory partition ForestDnsZones.pr.org.kh. This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and reload the zone. The event data is the error code. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 0d 00 00 00 ....andEvent Type: Error Event Source: DNS Event Category: None Event ID: 4007 DaPersonally I have not run into any problems with SP2. I manage quite a few Windows 2003 Servers and I have not run into a problem. If you're worried about driver compatibility you can research that with the vendor that the server came from, or if a custom built you can look into individual components. I personally would never configure a domain controller to have DNS point to anything but itself or another internal DNS server. I would not point a DC to an external DNS server. Pointing clients to another DNS server is probably alright, although if you configure DNS to use forwarders for external queries it isn't really necessary. You might not be doing this, you said only clients, so that might not be relevant. Can you access the internet when the DNS Server Service is stopped? IE ... telnet to port 25 or 80 of some external server that you reference by IP address, thus bypassing DNS resolution all together?
-
Jörgen Andersson wrote:
As a temporary solution, to allow you to leave your office, you could set the service to restart automatically. In the services console, doubleclick the dns-service (or rightclick and select Properties). In the properties window select the recovery tab and select your options on failure.
Thank you very much for your comment. That is one solution that could help me to temporary solve it.
Jörgen Andersson wrote:
You naturally need to address the issue why the service fails. But to help you with that we need more data, such as relevant entries in the event log.
That was my biggest challenge. I have checked in the event viewer and there is no entry that show me the reason why DNS server service is stopped. But I found the following error related to DNS server service that could give you some idea:
Event Type: Error Event Source: DNS Event Category: None Event ID: 4007 Date: 18-Jul-08 Time: 8:10:52 AM User: N/A Computer: SERVER Description: The DNS server was unable to open zone _msdcs.pr.org.kh in the Active Directory from the application directory partition ForestDnsZones.pr.org.kh. This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and reload the zone. The event data is the error code. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 0d 00 00 00 ....andEvent Type: Error Event Source: DNS Event Category: None Event ID: 4007 Date: 18-Jul-08 Time: 4:40:01 PM User: N/A Computer: SERVER Description: The DNS server was unable to open zone pr.org.kh in the Active Directory from the application directory partition DomainDnsZones.pr.org.kh. This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and reload the zone. The event data is the error code. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 0d 00 00 00 ....Please let me know if you have any solution with the above error escription. Thank in advance!!!If you get these eventlog entries when the server is started, then it's normal, the dns service has just started before the AD. Try to uninstall and reinstall the DNS role on the server. That will fix any eventual file and registry errors regarding the DNS, and it's done in ten minutes (no restart) so it won't really affect the users. About the servicepack: I always servicepack my computers a couple of weeks after the packs are released. They fix more problems than they create. And if there are any serious errors in them, it would create enough articles about it that it would raise above the normal internet noise. But of course, as always you need a proper backup before you do it!