windows xp - nslookup on XP resolves to address, but ping can't find host

06
2014-04
  • Fixee

    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
    • Answers
  • amiregelz

    Try clearing your cache:

    in cmd.exe:

    ipconfig /flushdns
  • slhck

    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"

    • Related Question

    windows 7 - Can ping IP address and nslookup hostname but cannot ping hostname
  • Puddingfox

    I have a DNS server set up on one of my machines using BIND 9.7 Everything works fine with it. On my Windows 7 desktop, I have statically-assigned all network values. I have one DNS server set -- my DNS server. On my desktop, 

     I can ping a third machine by IP fine.
 I can nslookup the hostname of the third machine fine.
 When I ping the hostname, it says it cannot find the host.

    /

    C:\Users\James>nslookup icecream
Server:  cake.my.domain
Address:  xxx.xxx.6.3

Name:    icecream.my.domain
Address:  xxx.xxx.6.9


C:\Users\James>ping xxx.xxx.6.9

Pinging xxx.xxx.6.9 with 32 bytes of data:
Reply from xxx.xxx.6.9: bytes=32 time<1ms TTL=255
Reply from xxx.xxx.6.9: bytes=32 time<1ms TTL=255
Reply from xxx.xxx.6.9: bytes=32 time<1ms TTL=255
Reply from xxx.xxx.6.9: bytes=32 time<1ms TTL=255

Ping statistics for xxx.xxx.6.9:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\James>ping icecream
Ping request could not find host icecream. Please check the name and try again.

    I have also specified the search domain as my.domain

    • xxx.xxx and my.domain substituted for security

    Why can I not ping by hostname? I also can not ping using the FQDN. The problem is that this problem is shared by all applications that resolve hostnames. I cannot use PuTTY to SSH to my machines by hostname; only by IP


    • Related Answers
  • Diskilla

    You could try editing your hosts file. Put there the hostnames and ip-adresses of your other machines. If thats not working try this: Your Router should be able to handle dns-tables for itself. Try to temporarly shut down your dns-server and clear all dns caches on all machines. Then restart your router and try it again.

  • 8088

    I faced the same problem in my network. When you use this command:

    ping icecream

    It uses WINS server since you have used icecream not icecream.my.domain.

    When looking for such words, Windows looks for NETBIOS names, but when you look for complete domain records, it will look in the DNS server. You can use one of the solutions below:

    1. Make sure you have correct records for that station in your WINS server.
    2. Use the complete domain name instead of using the host file. E.g. icecream.my.domain
  • 8088

    You don't have DNS suffixes configured. Either configure them, or use FQDN like this and it should work:

    ping icecream.my.domain
  • bendiy

    I'm looking for a permanent solution to this problem. I don't just have a problem with ping icecream, but also ping icecream.my.domain. It doesn't happen all the time, just randomly on one computer. ipconfig /flushdns fixes it sometimes and rebooting work as well, but it's not a permanent solution.

    I just tried this:

    Based on this:

  • user165568

    To disable this behaviour, disable Negative Caching by setting the value of NegativeCacheTime to 0 at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ Dnscache\Parameter