Netgear router forces clients to use it as primary DNS resolver

kosymodo

kosymodo

kosymodo

Associate
Joined
18 Jun 2020
Posts
398
Location
Warminster
I've recently changed my router from a TP-Link to a Netgear. I'm using Pi-hole for DNS queries. However, whereas the TP-Link was happy for the Pi-hole to be the DNS resolver, it seems the Netgear (even though I've set the Pi-hole as the only DNS server in the router’s settings) still forces clients to use it as their primary DNS resolver.

Does anyone have any experience of this, and any way of resolving it?
 
Majority of off-the-shelf 'home' routers, in my experience, work exactly like that, ie - user-entered DNS (Pi-Hole in this case) is set as a forwarder and the router's DHCP continues to dish out the router as the primary DNS.

You could use the DHCP server on the Pi-Hole, and disable it on the Netgear, though.
 
visibleman said:
Majority of off-the-shelf 'home' routers, in my experience, work exactly like that, ie - user-entered DNS (Pi-Hole in this case) is set as a forwarder and the router's DHCP continues to dish out the router as the primary DNS.

You could use the DHCP server on the Pi-Hole, and disable it on the Netgear, though.
Click to expand...

Thanks - I've not had (comparatively) much experience with 'home' routers, so haven't come across this before. I had the Pi-hole set up as my DHCP server before, was keen to try out the Netgear as DHCP server this time round, so easy for me to revert to Pi-hole DHCP server if need be
 
You must log in or register to reply here.
Back
Top Bottom