Windows 10: Fix nslookup works but ping fails in Windows 10

When querying the IP address of a website, if your nslookup works, but ping fails on Windows 10 PC, then there can be many reasons for that. Let’s try to resolve these issues, but before that here is what nslookup.exe and [...]

This post Fix nslookup works but ping fails in Windows 10 is from TheWindowsClub.com.

read more...

 

ping doesn't resolve hostname, but nslookup does

When PING doesn't work, the tracert doesn't work either, only nslookup works. So ping and tracert are both blocked by ICMP? Not sure how we can fix it. Thank you!

 

NSLOOKUP and PING do not match

I read many articles about the different results between nslookup and ping, but I somehow feel I do not fit in any of the explanations.

Scenario: Windows 10 (latest updates) connected to a corporate VPN via SSTP. The VPN connection is configured to suffix the corporate domain on the DNS queries (but on my tests I experimented removing and adding this). My hosts file is empty,
except the comments that comes by default. I did a flushdns just before the commands.

On the server side there is a corporate webserver with specific rules when the connection originates from the internal LAN (or VPN) or from the WAN. The correct behavior was already observed in the past, so this "works". Next steps is experimenting other
machines.

Use Case:

• With the VPN connected, nslookup will use the LAN's Default Server and not my ISP DNS -> OK
• NSLOOKUP a certain fully qualified host name will give me it's internal LAN address -> OK
• PING the same fully qualified host name will give me the public WAN address of the corporate domain -> Not OK, unless the VPN is disconnected, in that case de results would be OK.

Opening a browser with the same fully qualified host name goes into the WAN access limited page (load balancer rules detecting the origin remote address), although the client host (my PC) is in the LAN via VPN. Using chrome's "net-internal" page I see the
browser is resolving the WAN address instead of the LAN address (item 2 above).

Again, I know ping and nslookup do not resolve names exactly in the same manner, but there is no DNS cache and the hosts file is clean, I would still expect ping to resolve the internal LAN address in this case.

Any ideas on further troubleshoot why the browsers seems to be resolving the names incorrectly?

Note; It may be me, but this latest windows 10 upgrade/update seems to have broken the network. Just a gut feeling from some glitches in the last weeks.

 

DNS errors - nslookup works but ping doesn't after Windows 10 upgrade

I have various dns issues in my browsers. In testing, I have discovered that nslookup ALWAYS works but ping doesn't.

There are older Google results that suggest disabling ipv6 - but there does not appear to be ipv4 in Windows 10

ipconfig /flushdns cleared the problem but then it came back and I don't want to be jumping into the command prompt every 5 minutes

Any thoughts?

Thanks, Vincent