19

If I run ipconfig /all, in the DNS field it is showing numbers such as fec0:0:0:ffff::1%1, fec0:0:0:ffff::2%1 and fec0:0:0:ffff::3%1. nslookup www.google.com shows some kind of DNS error (lookup not found or similar). What does this mean and how do I fix it?

I didn't change any settings on my computer. I am supposed to be able to connect to the Internet as soon as I plug in the cable but this day the Internet stopped working for some reason. So when I checked ipconfig I saw those strange values.

This is what ipconfig shows about DNS:

user13267
  • 1,873

6 Answers6

15

Somehow you have enabled IPv6 on your node. Those are default IPv6 "site local anycast" addresses for DNS that Microsoft configures automatically if no other IPv6 DNS addresses are configured. They are obsolete (site local was deprecated in 2004, see Wikipedia). See also the IETF draft IPv6 Stateless DNS Discovery.

They are kind of like link local (fe80::), but can cross internal routers (link local won't cross any router). Microsoft DNS servers will accept DNS connections to any of those addresses, so this allows IPv6 DNS to work without any additional configuration. Not all DNS servers accept these.

Anycast means you can have several servers all publish the same address, but only one will actually accept any given connection from a client (different from multicast and unicast). Anycast is something new in IPv6.

You probably aren't actually using IPv6, so I suggest you configure some IPv4 addresses for DNS. You may want to disable IPv6, although somehow your node thinks it is available to you. Perhaps your ISP has started routing it to you - most will be doing that sooner or later. You should start learning it now, as IPv4 is on the way out - within a couple of months all the major RIRs will be out of public IPv4 addresses - the only public addresses available will be IPv6 from then on (except in very limited number, for very high prices). All but ARIN (N. America) are already out - APNIC ran out back in early 2011.

4

You are indeed using IPv6. This is the default address, something like the 169. addresses in IPv4 that Windows uses and indicates that you could not find a DHCP server when your machine requested a new address.

If you do an ipconfig /renew do you pick up a real address? Did you make changes recently to the networking configuration? Is this a home or work network and are other clients on the same network still able to resolve?

Please post the entire contents of ipconfig /all

2

I just had this issues, and I will focus on how I fixed it but I don't know how it happened.

  1. Disabled IPv6. This step may not be needed at all, but I tried doing step 2 on IPv6, and it didn't work. Maybe my gateway wasn't configured correctly for it.
  2. Enabled IPv4 to retrieve DNS from my gateway (router). Previously, it was set to localhost 127.0.0.1

Both of these are done in the Adapter settings: enter image description here

  1. Go to Control Panel -> Network and Internet -> Network Connections
  2. Right click on the Adapter and go to Properties
  3. Disable IPv6
  4. Got to the properties of IPv4
  5. Select "Obtain DNS server address automatically"

NOTE: this solution depends on your Gateway being configured to provide DNS Servers. Alternatively, you could directly provide the DNS server address(es) here.

Click OK and close out the settings.

That's all I had to do and it refreshed my DNS Server from my gateway. To verify your DNS Server:

ipconfig /all

Maybe try ipconfig /renew if that didn't work, reboot, etc.

0

If anyone comes across this issue again I know this was posted years ago but my solution was that for some odd reason in the properties of IPv6 these addresses were listed in the "Use the following DNS server addresses:" section of the properties of the network adapter. I did not put them there and this was a fresh clone of a machine in ESXi that did not have these in there as well.

AshRed
  • 1
-2

I KNOW THE PROBLEM!

You have Hamachi downloaded am I not mistaken? Your looking at the wrong part of the ipconfig! I just figured it out! Scroll up a litttle more to find your actual router config!

-4

go to your advanced adapter settings through the network and sharing center. uninstall all protocols, services, and clients. Then, install each group of them in this order: protocol service client

then click 'diagnose'

the issue should resolve itself.