DNS and Win2k Pro

  • Thread starter Thread starter Joe Markovich
  • Start date Start date
J

Joe Markovich

Hello Everyone:

I'm running 2k Pro SP4 and from time to time, DNS will
stop resolving names. Either I can run ipconfig /flushdns
or I will have to go into the properties of the network
connection, tcp/ip properties, and then make some random
change (like check or uncheck a checkbox) in the DNS tab
and then everything will work fine again. Obviously, this
is a giant pain to the users and to the techs.

My question is why is this acting like this? I have 2
other machines in the office (2k Pro SP4 also) that act
the exact same way.

All these machines are connected to a Linux firewall, and
in the clients' settings, I have the DNS servers entered
in of our ISP. Should I be doing this? We have other
client machines that are running 98 or NT 4 with those
same settings and they are fine..

Any help anyone could give me would be greatly appreciated!

Thanks, Joe.
 
In
Joe Markovich said:
Hello Everyone:

I'm running 2k Pro SP4 and from time to time, DNS will
stop resolving names. Either I can run ipconfig /flushdns
or I will have to go into the properties of the network
connection, tcp/ip properties, and then make some random
change (like check or uncheck a checkbox) in the DNS tab
and then everything will work fine again. Obviously, this
is a giant pain to the users and to the techs.

My question is why is this acting like this? I have 2
other machines in the office (2k Pro SP4 also) that act
the exact same way.

All these machines are connected to a Linux firewall, and
in the clients' settings, I have the DNS servers entered
in of our ISP. Should I be doing this? We have other
client machines that are running 98 or NT 4 with those
same settings and they are fine..

Any help anyone could give me would be greatly appreciated!

Thanks, Joe.
Click to expand...

Do you have a local DNS server?
Is this a Win2k or Win2k3 domain?
 
Remove the ISP's DNS entries from the clients. Point only to an internal DNS server. Make sure the internal DNS server does not have a "." root zone. If it
does, delete it. Also verify that the internal DNS is configured to protect against cache polution. If it still fails, try making manual queries via NSLOOKUP to the
internal server. If this fails, go to the internal DNS server and NSLOOKUP from it to the ISP's DNS. If this fails, then your ISP or your firewall isn't working. If it
works, then DNS cache polution appears to be the culprit.

Thank you,
Mike Johnston
Microsoft Network Support

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
 
Back
Top