nslookup IS working; ping -4 name.com NOT working#
The most obvious symptom of this problem is that nslookup
IS working, while ping -4 name.com
is NOT working.
That's because nslookup
contains its own DNS client, and so does not use the Windows one.
ping
when given a name, uses the Windows DNS Client to translate name -> number.
So if nslookup
can translate, then lots of things work: networking hardware, NIC adapter driver, internet connectivity to the DNS servers, and successfully accessing the servers to do a translation. That's a lot!
However, ping -4 name.com
fails, so if all that other stuff is working, it's the Windows DNS client software itself that is implicated.
Note i did ping -4
to isolate to IPv4 excluding IPv6 influences.
Best wayThat's why the best symptom to describe the actual problem is that