... unless your router intercepts and changes the client's DNS query destination address (like DNSFilter does in Merlin's firmware).What you set on the computer will rule out what the router is set too
ahhh! and that was what I was looking for. Then you do not have to monkey around with all the devices.... unless your router intercepts and changes the client's DNS query destination address (like DNSFilter does in Merlin's firmware).
Most home routers have their own built-in DNS server that does caching and forwarding to the upstream server(s) defined for the WAN interface. So clients should be configured to use that.Yet from an academic point of view it SEEMS to me the router should always trump any other device choice on DNS selection.... as it is the manager of the traffic out to internet. At least that is how I think about it.
Yet from an academic point of view it SEEMS to me the router should always trump any other device choice on DNS selection.... as it is the manager of the traffic out to internet. At least that is how I think about it.
This seems to be the case. My router has Cloudflare DNS (1.1.1.1 & 1.0.0.1) setup. However when i change the DNS to 8.8.8.8 on a local PC connected to the router, that PC is now using google DNS. So it appears the DNS address on the client overides the DNS on the router.What you set on the computer will rule out what the router is set too
Sent from my SM-G981U1 using Tapatalk
thanks...DNS queries are made by clients, therefore it's not the job of the router to hijack and redirect these - that would be a non-standard behaviour, which can break various things. For instance if you wanted to configure your children's computer to use a DNS server such as Cleanbrowsing, or you had a Windows domain controller.
What a home router normally does is provide clients with the address of the DNS they can use, when these clients use DHCP to obtain network parameters. A client choosing to use hardcoded settings rather than obtaining them through DHCP should then be the ones to decide since DNS resolving is their job, not the router.
All a router can do in a clean design is present itself as the LAN's network resolver, so it can act as a cache. Blindly overriding should be considered non-standard, and be purely optional.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!