DNS stops reponding?

  • Thread starter Thread starter Steve Grosz
  • Start date Start date
S

Steve Grosz

I have a issue where my Win2003 server which is running DNS just seems
to stop responding to requests randomly. I will try a tracert to some
of the sites hosted on this box, and get nothing back. Once the machine
is restarted, it works fine.

I've checked the event logs for DNS errors, and don't find any. Its
running on a P4 2.8gig hyper-threaded CPU, so I don't think its a
problem with the processor or machine getting overloaded with requests.

I've also checked the DNS settings, timeouts, etc (using DNSreport.com)
and it says all looks good)

Any suggestions, or I can provide more info if needed.

Steve
 
Steve Grosz said:
I have a issue where my Win2003 server which is running DNS just seems
to stop responding to requests randomly. I will try a tracert to some
of the sites hosted on this box, and get nothing back. Once the machine
is restarted, it works fine.
Click to expand...

First, this isn't likely a DNS problem since you
seem to be resolving names (tracert doesn't really
begin until you get the name resolved.)

Although no one much minds if you can get help you
have also posted a Win2003 problem to a Win2000
newsgroup but we will try to help anyway...
I've checked the event logs for DNS errors, and don't find any. Its
running on a P4 2.8gig hyper-threaded CPU, so I don't think its a
problem with the processor or machine getting overloaded with requests.
Click to expand...

Do you get the intermediate router responses?

Does the name resolve to an IP?
I've also checked the DNS settings, timeouts, etc (using DNSreport.com)
and it says all looks good)
Click to expand...

But you seem to be having trouble with general responses
(tracert) or your web sites rather than DNS specifically...
Any suggestions, or I can provide more info if needed.
Click to expand...

Figure precisely what is not working. All of the server,
one service (e.g., just DNS or web)

What is the server DOING when you logon there locally?
 
Herb said:
First, this isn't likely a DNS problem since you
seem to be resolving names (tracert doesn't really
begin until you get the name resolved.)
Click to expand...

Let me clarify, when I'm having this problem, and try a tracert, I get
nothing back, so the name isn't being resolved.

Although no one much minds if you can get help you
have also posted a Win2003 problem to a Win2000
newsgroup but we will try to help anyway...




Do you get the intermediate router responses?

Does the name resolve to an IP?
Click to expand...

The name (when it does resolve) does resolve to a IP, yes.
But you seem to be having trouble with general responses
(tracert) or your web sites rather than DNS specifically...




Figure precisely what is not working. All of the server,
one service (e.g., just DNS or web)

What is the server DOING when you logon there locally?
Click to expand...
Its seems that when this problem is occuring, DNS and IIS stop responding.

I'm haven't actually been at the server when the problem is occuring,
I'll call and have someone simply restart the box, and the problem stops.

Steve
 
Let me clarify, when I'm having this problem, and try a tracert, I get
nothing back, so the name isn't being resolved.
Click to expand...

Generally when one uses tracert it is because they
have already tried ping or some other tool and
can see that the name is resolving -- tracert if primarily
for seeking the PLACE along the (routed) path
where the message is being lost.

And anytime you have a connectivity problem you
should try the NAME vs. the actual IP address --
if name fails while IP works you do in fact have
some type of name resolution problem.

Have you tried direct queries to the DNS server
using NSLookup?

Do you know which DNS server your client machine
is using?

Have you tried to isolate the DNS issue?
 
Herb said:
Generally when one uses tracert it is because they
have already tried ping or some other tool and
can see that the name is resolving -- tracert if primarily
for seeking the PLACE along the (routed) path
where the message is being lost.
Click to expand...

I always use the name, never the IP.
And anytime you have a connectivity problem you
should try the NAME vs. the actual IP address --
if name fails while IP works you do in fact have
some type of name resolution problem.

Have you tried direct queries to the DNS server
using NSLookup?
Click to expand...

I haven't tried it when the problem is occuring, but in general, it
reports back the correct DNS server.
Do you know which DNS server your client machine
is using?
Click to expand...

No, I don't. Its a work machine.
Have you tried to isolate the DNS issue?
Click to expand...

Aside from checking the DNS event log files, not sure how to isolate the
issue, I guess that's the sort of help I was hoping to find!! :)

Steve
 
Hi Steve

Perhaps you could just restart the dns server service to confirm that this
is the issue rather than rebooting the entire machine?

Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.
 
I always use the name, never the IP.
Click to expand...

So now you have learned one of the most important IP
troubleshooting methods: name vs. IP
No, I don't. Its a work machine.
Click to expand...

You will likely need this kind of info to isolate the
problem.
Aside from checking the DNS event log files, not sure how to isolate the
issue, I guess that's the sort of help I was hoping to find!! :)
Click to expand...

Name vs. IP, specific tools like NSLookup etc.
 
Steve Grosz said:
I haven't tried it when the problem is occuring, but in general, it
reports back the correct DNS server.
Click to expand...

Nslookup is reporting this when you invoke it?
Which server is that?

No, I don't. Its a work machine.
Click to expand...

Now I'm confused. You just said it (assuming "nslookup"), reports the
correct DNS server above. Nslookup in this case just told you which DNS
server it's using, unless I am misunderstanding something here.

Just an FYI, you can also do an ipconfig /all on the client machine and it
will tell you which DNS server(s) it's using.



--
Regards,
Ace

G O E A G L E S !!!
Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
Back
Top