Ping unable to resolve but nslookup works fine – workaround

Sometimes if you make changes to your local DNS server windows do not works ok to resolve this DNS record in a local network.

What?

Why?

On Windows (even recent versions such as Windows 10), the first step can easily fail. For the sake of backward compatibility, Windows supports various methods of hostname resolution (hosts file, DNS, NetBIOS/WINS, LMHOST file).

Unfortunately, it seems that Windows’ ping command doesn’t always attempt a DNS lookup. I don’t know the specific conditions that trigger this behavior.

Fortunately, we can force Windows to do a DNS lookup by using an FQDN (fully qualified domain name). In practice, we do this by suffixing a . dot to the hostname: ykylo.. Try ping ykylo.and verify that it works.

Workaround 0!

Try adding . to the DNS suffixes for that connection. I.e, go to:

  1. Ethernet Status
  2. Click Properties
  3. Internet Protocol Version 4
  4. Click Properties
  5. Click Advanced
  6. Append these DNS suffices (in order)
  7. Add . as a suffix

Workaround 1!

Some commands that will reinitialize various network states :

Reset WINSOCK entries to installation defaults : netsh winsock reset catalog
Reset TCP/IP stack to installation defaults : netsh int ip reset reset.log
Flush DNS resolver cache : ipconfig /flushdns
Renew DNS client registration and refresh DHCP leases : ipconfig /registerdns
Flush routing table : route /f (reboot required)

0
Comments

Leave a Reply

Your email address will not be published. Required fields are marked *

14 + fourteen =

© 2018 David Stein