Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I don't know Windows very well. This is Win XP SP3. nslookup resolves hostname fine, but ping (and other DNS-users on the machine like Chrome) cannot resolve the same hostname. ping works fine with explicit IP address.

Is this a bug in XP?

C:\>nslookup blade.haq.loc
Server:  dns.haq.loc
Address:  10.10.10.16

Name:    blade.haq.loc
Address:  10.10.10.22


C:\>ping blade.haq.loc
Ping request could not find host blade.haq.loc. Please check the name and try ag
ain.

C:\>ping 10.10.10.22

Pinging 10.10.10.22 with 32 bytes of data:

Reply from 10.10.10.22: bytes=32 time=1ms TTL=63
Reply from 10.10.10.22: bytes=32 time<1ms TTL=63
Reply from 10.10.10.22: bytes=32 time<1ms TTL=63
share|improve this question
1  
possible duplicate of Why is 'ping' unable to resolve a name when 'nslookup' works fine? – TFM Nov 27 '12 at 3:57

Try clearing your cache:

in cmd.exe:

ipconfig /flushdns
share|improve this answer

Try running the command:

ipconfig /flushdns

If that doesnt resolve the problem, then there could be a possible conflict with your DNS server.

So if it doesnt work,

  • Go into "Network and Sharing Center"
  • Open up the connection that you are using
  • Go to Properties
  • Look for the IPv4 Address
  • And assign it a specific DNS server, try using Google's Public DNS servers "8.8.8.8, 8.8.4.4"
share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .