Dns – XP Computer does not resolve DNS

browsingdns

I'm unable to figure out why this one computer on a network cannot resolve URLs. When an address is typed in, the message "Page cannot be displayed" is shown. When the IP is typed in, the page loads. Google was used as a test site.

  • The computer obtains a valid IP through the server.
  • The computer obtains a valid DNS through the server.
  • There is no proxy.
  • There are no erroneous HOST file entries.
  • Windows Firewall is off and no other firewall programs are loaded
  • Cannot ping sites with URL. (i.e. www.google.com receives "Ping request cannot find host www.google.com")
  • Can ping site if IP is used instead of URL. (i.e. 74.125.224.48 "Ping replies received")
  • DNS service on workstation was stopped and started.
  • Computer was rebooted as well as cold booted.
  • Changing the DNS manually to different servers did not fix. (8.8.8.8; 208.67.222.222; 208.67.220.220; internal DNS)
  • IPCONFIG /flushdns after each DNS change did not fix.
  • IE, Firefox, Chrome are all affected.
  • No malware detected on full scan using AVG, Malwarebytes and SuperAntiSpyware.
  • Checked for rootkit with TDSSKiller and none detected.
  • Server is able to browse without issue.
  • Other computers on network can browse without issue.

Any suggestions for what to try next or ideas about what is possibly going on would be appreciated.

Best Answer

You want to a use a tool called nslookup. This is command-line tool that is included with Windows, so you already have it. Just open a command prompt, type nslookup, and press enter. Then you can start entering names to resolve. You can change the server it checks against by type "server x.x.x.x", where x.x.x.x is the IP of the new server. Type "quit" when finished.

The other thing I would check is IPv6. You may have a dns server that's returning IPv6 addresses, or a machine that is sending out IPv6 address requests, and then a browser that only knows IPv4 routes to the web.

After that, if and only if you still haven't found the problem, you can try a reset of your ip stack. From a command prompt:

netsh int ip reset resetlog.txt

Related Question