Windows 7 issue with DNS resolving
Hi,
I'm running Windows 7 Starter on a laptop having issues with name resolution.
nslookup www.google.com gives proper result incl. all addresses and aliases.
Immediately followed by ping www.google.com results in:
"Ping request could not find host www.google.com. Please check name and try again."
Ping for one of the given IP by the first nslookup works just fine.
Anyone having a clue what's going on here?
Greetings
Christian
June 9th, 2011 7:32am
When you do nslookup for google, you may be getting an ip address,Try to ping the ip address, see if you get reply for that or not?
Also are you able resolve and ping internal dns names?If internal names are able to resolve are you able to connect to the internet?
If you are having issues with that in the preferred dns enter 4.2.2.2 and see if that helps.
Free Windows Admin Tool Kit Click here and download it now
June 9th, 2011 9:11am
As I said- when I ping the IP address which nslookup tells me this works fine!
Same happens for internal hosts- nslookup tells me the IP address. I can ping the IP address, but not the hostname. No difference if I try to ping fqdn or shortname.
It is not a nameserver issue- as nslookup just works fine. And any other host in the network is resolving through the same name server everything properly.
Where should I look for root cause?
June 9th, 2011 9:18am
If you are looking to find a root cause, take a trace while you ping the ip and see where is the packet getting dropped or not getting proper response.
Please go to the following URL to download Microsoft Network Monitor 3.4
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=983b941d-06cb-4658-b7f6-3088333d062f&displaylang=en
Free Windows Admin Tool Kit Click here and download it now
June 9th, 2011 10:07am
Try to scan your laptop by using antivirus/anti-malware program with latest signature, just to make sure your laptop is not infected with worm/virus.
You could also test to configure following free DNS servers provided by
OpenDNS, see whether it helps.
208.67.220.220
208.67.222.222
Hope this helps.
dawooddoe
Home Network & Wireless Network Help
June 9th, 2011 11:06am
nslookup www.google.com gives proper result incl. all addresses and
aliases.
Immediately followed by ping www.google.com results in:
"Ping request could not find host www.google.com. Please check name
and try again."
Ping for one of the given IP by the first nslookup works just fine.
Fire up an elevated (as admin) command prompt, "cd" to your
%systemroot%\system32\drivers\etc folder and then enter the
command "notepad hosts" (no quotes) and check if "google"
is listed in there, if so, and in case you'll find it along with some
other names, your system may have been compromised by
some kind of malware, in this case, please download this tool
http://connect.microsoft.com/systemsweeper
burn it on a CD and use the CD to boot your system, then
proceed to a full scan and clean; at end, ensure to reset your
hosts file following the direction you'll find here
http://support.microsoft.com/kb/972034
HTH
Free Windows Admin Tool Kit Click here and download it now
June 9th, 2011 11:41am
Hi all,
thanks for trying to help. But nothing really explains the issue.
Meanwhile I found a solution- I had OpenVPN installed and for some reason this screwed up routing (even though it wasn't connected).
Now all works fine.
But I'd try to understand why this appeared- why is the DNS client service (?) using different ways to resolve compared to nslookup?
Greetings
June 10th, 2011 12:52am
Meanwhile I found a solution- I had OpenVPN installed and for some
reason this screwed up routing (even though it wasn't connected).
OpenVPN installs a virtual adapter and if the adapter is enabled,
even if the VPN isn't connected it may cause some issues... if
the OVPN wasn't properly configured and if the adapters binding
and priority weren't correctly set
Free Windows Admin Tool Kit Click here and download it now
June 10th, 2011 3:29am