Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

DNS problem

Status
Not open for further replies.

Russmis

MIS
Oct 22, 2002
71
US
Hello all, I have a problem with a DNS server. I will try to explain. We have one domain controller that runs windows 2000 server. Server runs DHCP and DNS. (server has static ip). I don't know exactly the time, but I had to reboot this server two times already in the period of two weeks. This is a problem, users can't open some websites, or send emails, after rebooting a server everything is fine. Today I setup Forwarders to my isp so it gets DNS records from their server, maybe this will help.

Anyone has any ideas, am I correct that this is a DNS problem, what can I check or change?
 
Russmis,

What is they symptom when you have to reboot the DC? Does the DC lock up, or is DNS the only problem? Have you tried any diagnostics (such as pinging from the DC) before rebooting?

Wishdiak
A+, Network+, Security+, MCSA: Security 2003
 
When I reboot, I did not see any lock ups, yes, ping to outside, but did not ping inside. I also, updated from sp3 to sp4, this is after a prob happend, so I will see if it fixed it. DNS was working for 2ys, so I don't know what happend.
 
Strange, I have developed the same issue on a Win 2000 server in the last month...

Suspect I have a memory leak, but it came out of the blue, nothing but MS patches added in quite a while. On mine Lsass.exe appears to grow in memory use(not done monitoring). Last week DNS appeared to act like yours, I had to reboot to have a responsive DNS.


........................................
Chernobyl disaster..a must see pictorial
 
Next time this happens, please try using NSLOOKUP before you reboot the server to see if the problem is really with name resolution, or if it is something else.

Open a command-line, and type NSLOOKUP.

You will see a response letting you know that it is pointed at your local DNS server.

Then type in a host on the outside, like or something. If it resolves, you know that your server is able to make queries on your behalf. Then try pinging that host by name. Then try to browse to that website. Let us know at what point things don't work.

Also, when your clients can't browse out, can your server? And are you running ISA as a firewall, or are you using a hardware device?

ShackDaddy
 
ShackDaddy:

Ok, I will try that. Yes, we do have pix firewall, no ISA. None of the server or user can browse internet or send emails when this happens.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top