nslookup resolves ip but IE6 get DNS error

  • Thread starter Thread starter Brock
  • Start date Start date
B

Brock

I have a win2000 server running Terminal Service. after 8 hours of running
find with now prob. IE can nolonger resolve url ns can nolonger see DC but
can open a terminal session. after a reboot the same thing happens after 8
hours. Help?
 
IE uses the DNS Client cache; NSLookup does not
so look for bad (even negative) responses in the cache.
ipconfig /displayDNS

(Note, negative responses are only cached for 5 minutes so
this is unlikely to be the cause of a long term problem.)

Also check: The affect client NIC must have ONLY internal
DNS servers, not a mixture of internal and external (e.g., the
ISP).
 
So you can't have internal and external dns settings? Why does it work for a
while?
Thanks,
Brock
 
Brock said:
So you can't have internal and external dns settings? Why does it work for a
while?
Thanks,
Brock
Click to expand...

That's because of the way the DNS client resolver works. It will check the
first entry, if no answer or timeout, it will remove it from the eligible
resolver list then go to the next one. The list does not reset unless you
restart the machine, restart the DNS client service or renew an ip. This is
documented.

You need to ONLY use your internal DNS on all AD members (DCs and clients)
to insure proper AD functionality.

So what you're saying, if resolution works sometimes, then my feeling is
that your internal DNS has the Root zone present, which needs to be deleted.
Configure a forwarder for efficient Internet name resolution. If not sure
about these two steps, see this article, it shows how:
http://support.microsoft.com/?id=300202

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
So you can't have internal and external dns settings? Why does it work for
a
while?
Click to expand...

It might work accidentally or intermittently. The machine normally
"latches" on
to the first server unless it goes down then it may latch onto the second
which
could be external and even if the first comes back online it may not
(immediately?)
return to it.

It doesn't work reliably and the fix is simple (and reliable):
Point to the internal, let it recurse or forward to a DNS that can
resolve the Internet.
 
Back
Top