Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

My Win7 box is erroneously resolving a IP address.

I had the same problem last week and "fixed" that by switching to Google Public DNS 8.8.8.8 and 8.8.4.4 for IPV4 and the others for IPv6.

So when I do an ipconfig /all it says the DNS servers are indeed pointing at Google but on any other outside system this resolves just fine, internally however it does not.

When I do a tracert it resolves to the wrong address as with a Ping.

When I say the wrong address it resolves to the correct server but Im using a secondary IP on the server for a website and it's resolving to the servers primary IP not the secondary so the site 404s "only on this machine" so it's not a server setup issue.

Ive checked the Hosts file in etc/Drivers and no entries are in there.

The machine itself it on a LAN, not really sure of its status, I dont think it's being controlled by a domain as it's just in Workgroup>Workgroup with no DOMAIN prefix as I would normally expect.

It is getting it's IP from a DHCP server but as above I am overriding the DNS settings locally with the

Use the following DNS server addresses

which is showing up in IPconfig as I would expect 8.8.8.8 etc.

So my question is what else could be overriding the resolution of my domain name to the proper IP address between my machine and the internet.

UPDATE:

I should also add that if I put an entry INTO Hosts file for the domain >> IP it will resolve correctly. So it's not being "absolutely" overridden / hijacked.

UPDATE 2:

Using NSLookup I get the following for both my domain and even just for www.google.com

It would seem that 1: The machine is using IPV6 by default (is this normal?) and 2. it's not resolving properly via Google Public DNS on IPV6

So if 2 is correct ,would this mean the machine will fall back to using LAN DNS settings??

enter image description here

share|improve this question

1 Answer 1

use nslookup to troubleshoot:

Released with Windows 2000 and later versions, Nslookup is a command-line tool that lets you test and troubleshoot Domain Name System (DNS) resolution. To start nslookup, open a command prompt and enter nslookup, see Figure A. Nslookup will display the machine's default DNS server and IP address. You can now enter nslookup commands. Enter help at the nslookup prompt for a quick list of commands.

enter image description here

To enter the interactive mode of nslookup, type in the nslookup command with no options. While in interactive mode you have many more options available to you. To quit interactive mode, type exit on a line by itself and press enter.

By default, nslookup uses whatever your default DNS server is to test your resolution, but you can choose a different DNS server to test your resolution. This allows you to verify if an error is on the server, if there is a widespread resolution error, or if the server is possibly down. Nslookup will also display the various types of DNS records, not just primary (A) records, or all records for a domain.

share|improve this answer
    
Thanks, please see my update 2. Any thoughts? –  rism Mar 10 at 22:33

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.