DNS server.

Hi,

I tried to change the DNS server earlier on the Talk Talk hub using google DNS (pic 1) i saved the setting and when i rebooted the router i went back into the router settings to check if it worked i found the value had not changed under the "Device info" tab (pic 2) but the Google DNS was still listed as the DNS server when i clicked the DNS tab.

Could someone tell me what i am doing wrong, thanks.

Pic 1 - https://i.postimg.cc/Z5VTjzVj/dns.jpg

Pic 2 - https://i.postimg.cc/L6z4Y0w4/dns3.jpg

.

What DNS servers are your DHCP connected clients receiving?

Is there an option to download the config file? It possibly has that 79 stuff in that, and the GUI change is not used to overwrite it.

Basically locking it down unless you edit the config file and "restore" it. Which I don't really recommend even if it lets you. Unless you have a spare router that works on the line.

Thanks for answering i got it sorted on Kitz forum -

Pic 2 is showing what TalkTalk hands to the "hub", along with the public IPv4 address, when establishing the connection. You Pic 1 shows what the "hub" will actually use.

From a command prompt ipconfig /all should show DNS in use by the network card. This is for PC, but I think Linux is the same.

Sorted -
DNS Servers . . . . . . . . . . . : 8.8.8.8
8.8.4.4
NetBIOS over Tcpip. . . . . . . . : Enabled

In reply to a post by pluralist:

Is there an option to download the config file? It possibly has that 79 stuff in that, and the GUI change is not used to overwrite it.

Assuming the router has a fundamental bug in its software is not necessarily the place to start diagnostics. In fact the router is working in the same way as pretty much all others. As the OP found on Kitz.

So no problem in reality. Just a “user perception” issue as clients are being issued the correct / nominated DNS severs via DHCP.

In reply to a post by Pheasant:

So no problem in reality. Just a “user perception” issue as clients are being issued the correct / nominated DNS severs via DHCP.

Yes, just a mismatched expectation of what the web UI should show.

Most people aren't aware typically most home routers act as DNS proxy and forward to the ISP DNS, and by changing the local DHCP settings the clients just bypass the router proxy / cache.

In reply to a post by Pheasant:

So no problem in reality. Just a “user perception” issue as clients are being issued the correct / nominated DNS severs via DHCP.

You nailed it, i thought it would show the same DNS under both tabs but as has been explained that's not how it works.

Ta!

If you want to verify what DNS servers are actually being called you can use a site like https://ipleak.net/

I've never found my ISP ones a problem, except a couple of times when they had faults. That's at least eight providers. Currently Three Mobile and Three HomeFi router.

In reply to a post by pluralist:

I've never found my ISP ones a problem, except a couple of times when they had faults.

So you have never found your ISP's DNS a problem, until they gave you problems, i think that is what most of us who have had DNS issues will have found.

.

Edited by Jack_Hackett (Sun 30-May-21 17:11:07)

A couple of faults spilt amongst 8 providers over a period of something like 30 years doesn't sound like a problem to me .

Given that any provider's network can and does go down more than that, so you can't do anything whatever DNS servers you use ....

In reply to a post by pluralist:

A couple of faults spilt amongst 8 providers over a period of something like 30 years doesn't sound like a problem to me .

Given that any provider's network can and does go down more than that, so you can't do anything whatever DNS servers you use ....

Mine hasn't gone down i am having issues with one sitre only all others work as they always have.

In reply to a post by jchamier:

In reply to a post by Pheasant:

So no problem in reality. Just a “user perception” issue as clients are being issued the correct / nominated DNS severs via DHCP.

Yes, just a mismatched expectation of what the web UI should show.

Most people aren't aware typically most home routers act as DNS proxy and forward to the ISP DNS, and by changing the local DHCP settings the clients just bypass the router proxy / cache.

Yes thought as much initially, which is why I asked what DNS was actually being served to clients in my first post. No point chasing your tail thinking you have a problem but don’t. OP subsequently confined that all is good in the hood.

DNS is one of the easier ways to track what people do on the internet. I wouldn't use Google DNS for this reason.

A Raspi running piHole and and Unbound is easy to setup following online guides and Unbound use the authoritative DNS servers so if these are down, the site is down for everyone.
DNS requests can also be secured so no one entity is tracking all your requests and selling them on.

In reply to a post by smouty:

DNS is one of the easier ways to track what people do on the internet. I wouldn't use Google DNS for this reason.

I am now using Cloudflare 1.1.1.1 after doing a bit of research.

https://digital.com/cdn-providers/cloudflare/

.

In reply to a post by Jack_Hackett:

I am now using Cloudflare 1.1.1.1 after doing a bit of research.

There is also Quad 9 as another alternative. But if you stream a lot of content you might find your ISPs servers give faster more reliable streams for other reasons.

In reply to a post by jchamier:

In reply to a post by Jack_Hackett:

I am now using Cloudflare 1.1.1.1 after doing a bit of research.

There is also Quad 9 as another alternative. But if you stream a lot of content you might find your ISPs servers give faster more reliable streams for other reasons.

Thanks.

More grist for your mill…

https://www.howtogeek.com/342330/how-to-choose-the-b...

In reply to a post by Pheasant:

More grist for your mill…

https://www.howtogeek.com/342330/how-to-choose-the-b...

Thanks i did some testing yesterday using that.

https://i.postimg.cc/ZRnPzkGC/bbbbb.jpg

https://i.postimg.cc/ZRCRYkpg/dns.jpg