I have a W2K3 box running the DNS Service that appears to just cease to function; no one is albe to surf the web. The reason I say appear is because we do an nslookup on the dc and we get request time out....we stop and restart the dns server/client then everything starts working again.
Any idea what could be going on here?
TIA
This conversation is currently closed to new comments.
did you see this: DNS clients may not be able to access sites where the CNAME resource record for the site has been cached on a Windows Server 2003 DNS server View products that this article applies to. http://support.microsoft.com/kb/873430/en-us
Did you set timeout=10 or something else... just change the default because it's like 2 seconds and that's not enough in many cases? If you still have the problem, did you try to check the servive state in the list of services in windows... to see if it was stopped? And eventually just restart the service instead of restarting the server?
It may be a wrong set of command that just ask the dns to stop. A backup, an update or something like that???
If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.
DNS Failure - No EventID
I have a W2K3 box running the DNS Service that appears to just cease to function; no one is albe to surf the web. The reason I say appear is because we do an nslookup on the dc and we get request time out....we stop and restart the dns server/client then everything starts working again.
Any idea what could be going on here?
TIA