Strange issue with a dodgy DNS server?

TheDeerDude · 15 Apr 2018

This is a fresh install of Windows 10.

I used nslookup in cmd to look up an IP of a website. Here are the results:

Code:

C:\Users\Username>nslookup www.google.com
Server:  UnKnown
Address:  fe80::a08f:4f72:28c5:81c1

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to UnKnown timed-out

This seemed strange to me, so I checked my DNS server settings for IPv4, and, out of the blue, it seems to have set itself to 127.7.7.6 IPv6 is also set to a manual address of "fe80::a08f:4f72:28c5:81c1"

Why is that, and can anyone explain it? Is it something to be worried about? Websites load fine, everything works, but it doesn't seem right to me.

Samuria · 15 Apr 2018

Set dns to 208.67.220.220 and 1.1.1.1 te setting you have is something running on your pc as its local address do you have and security or anti virus software that often does it to scan incoming requests. Do you get a reply if you put the 127.7.7.6 into a browser?

TheDeerDude · 15 Apr 2018

I tried changing them to "obtain automatically" and then to the IPs you provided, but they kept defaulting to the previous IP.

Now that you mention it, I do - I am running Heimdal Pro with its "Traffic Scanning" features enabled. I disabled them temporarily, and I was able to change the IP configuration to what I wanted. Would it be safe to assume that it's Heimdal then, and nothing is wrong?

I get no reply from 127.6.6.7 in the web browser

Samuria · 15 Apr 2018

Heimdal Pro sounds a good idea but could give problem updating things on it own it would beinteresting to do a speed test with it off and wit hit on as the dns must be slower

Digital Life · 16 Apr 2018

Not sure why nslookup failed it should work since you have a set DNS server, This should work:

Code:

nslookup google.com 127.6.6.7

TheDeerDude · 16 Apr 2018

Samuria said:

Heimdal Pro sounds a good idea but could give problem updating things on it own it would beinteresting to do a speed test with it off and wit hit on as the dns must be slower

I think I'll pass, I'm not even sure how I would go about that. I just wanted to make sure it wasn't something malicious changing my DNS servers. Your guess about the security software doing this was spot on, thank you

sml156 said:

Not sure why nslookup failed it should work since you have a set DNS server, This should work:

Code:

nslookup google.com 127.6.6.7

Well, that works! I don't know why but by default it's using the set IPv6 address for this, but when using that command, it works.

f14tomcat · 16 Apr 2018

TheDeerDude said:

I think I'll pass, I'm not even sure how I would go about that. I just wanted to make sure it wasn't something malicious changing my DNS servers. Your guess about the security software doing this was spot on, thank you

Well, that works! I don't know why but by default it's using the set IPv6 address for this, but when using that command, it works.

Just FYI.... this is pretty much the most common Speed Test used, least here in TF. There are others, this is the most common. It doesn't install anything. Easy....

https://www.speedtest.net/

TheDeerDude · 16 Apr 2018

f14tomcat said:

Just FYI.... this is pretty much the most common Speed Test used, least here in TF. There are others, this is the most common. It doesn't install anything. Easy....

https://www.speedtest.net/

Oh, I'm aware of the site - used it plenty of times before! Thank you though

I just figured, DNS servers have no impact of the speed of your connection? Once your computer finds the domain's address, it shouldn't matter, should it? It's only about the time it takes to look up the domain. I didn't think this test was relevant

f14tomcat · 16 Apr 2018

TheDeerDude said:

Oh, I'm aware of the site - used it plenty of times before! Thank you though

I just figured, DNS servers have no impact of the speed of your connection? Once your computer finds the domain's address, it shouldn't matter, should it? It's only about the time it takes to look up the domain. I didn't think this test was relevant

You're correct. Just posted that cause you mentioned "I'm not even sure how I would go about that". Guess you were referring to something else. No, far as I know, the DNS server has nothing to do with speed. Hops, jumps, and traffic congestion, re-routes...all that nasty stuff affects the speed. A speed test, like Ookla, is basically how fast can you ping the closest server, and back 'n forth. It just sends/receives little trash packets. Hardly a real world scenario. But, getting OT.....