Re: NSLookup vs. Ping results
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Tue, 31 May 2005 19:54:48 -0500
"D0Thomas" <D0Thomas@xxxxxxxxxxxxxxxxxx> wrote in message
news:#F30q1gZFHA.980@xxxxxxxxxxxxxxxxxxxxxxx
> What would cause the Ping command to not resolve an address (such as
> www.yahoo.com) when the NSLookup utility can resolve the address just
fine?
>
> I have a win2000 client that can ping the IP address directly
> (68.142.197.80) but when I ping www.yahoo.com it says host not found.
Yet,
> typing NSLOOKUP www.yahoo.com resolves the addresses ok.
>
Most likely reason is client side cache is wrong, but a
negative cache entry is only 5 minutes so that would imply
it didn't last long or that you actually had a wrong (but
actual) answer in the cache.
If you eliminate the client side cache it might be due to
the nslookup using a different set of DNS servers (e.g.,
internal vs. external) than the ping (client computer)
resolver.
This comes from mistakenly trying to us two 'sets' of
DNS servers on the client NICs.
Internal Clients MUST use strictly the internal DNS
servers -- and these internal DNS server must be
responsible for resolving/forwarding any external name
requests.
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
.
- Prev by Date: Re: How to alter DNS with CMD command?
- Next by Date: Re: How to alter DNS with CMD command?
- Previous by thread: Re: How to alter DNS with CMD command?
- Next by thread: Re: NSLookup vs. Ping results
- Index(es):
Relevant Pages
|
