Re: NSLookup vs. Ping results
- From: "Ace Fekay [MVP]" <PleaseSubstituteMyActualFirstName&LastNameHere@xxxxxxxxxxx>
- Date: Tue, 31 May 2005 22:47:37 -0400
D0Thomas wrote:
> 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.
>
> TIA
In addition to Herb's post, the nslookup command has it's own resolver
service, but the ping command uses the system's resolver service, which can
include other factors, such as what Herb mentioned about what DNS servers
are listed, the client side cache, which gets populated from what's in the
hosts file and previous queries.
Plus nslooku is a strict DNS query over UDP 53. Ping relies on the system to
query it.
Are you having any problems with resolving other names?
--
Regards,
Ace
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
Paramount: What's up with taking Enterprise off the air??
Infinite Diversities in Infinite Combinations.
=================================
.
- Prev by Date: Re: How to alter DNS with CMD command?
- Next by Date: Re: Problems with the DnsAvoidRegisterRecords registry key
- Previous by thread: Re: NSLookup vs. Ping results
- Next by thread: Re: Problems with the DnsAvoidRegisterRecords registry key
- Index(es):
Relevant Pages
|
