NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Netgear R6220 - Disable DNS Relay
Hi, I'm using a R6220 in my home network. I'm using even a RaspberryPi with PiHole installed in it, so I can block ads and some other domains that reduce my band (60mbps fttc). Now, I've found out t...
Not sure what you're meaning by this.
When you submit a request, the request goes to the router and the router determines whether to use the DNS that you set up or the automatic one through the ISP.
If you want it skipping the dns going to the router, you'd have to set that up through your device (computer, phone, tablet, etc). some devices allow the custom DNS through their own settings.
If this isn't what you're refering to, then I need a little more clarity on what you're doing/trying.
So, now the DNS request route is: Client -> Router -> DNS Server.
In my project has to be: Client -> DNS Server.
Bypass the request on the router.
I've found out it because PiHole returns an error, it blocks requests from router IP because they are too much for him. In fact this makes a DNS relay, so every request pass trought the router, not directly on the local DNS server.
This, in addition to generating the error on pihole, slows down the response to queries.
I know that configuring DNS directly on clients would fix, but I can't do it on every device on the newtwork... I want to be an automatic setting that DHCP server sends to clients, even when a new device is connected. Otherwise I have to use the DHCP on PiHole and not the original one of the router.
But not relaying on the router.
so let me pose a question.
If the router isn't involved and it is just supposed to go client---->dns relay, how do you expect the router to tell the client anything? Its not involved.
For that to happen, it has to be done on the client side.
I use pi-hole on my network so I've played with it a bit. I'm not sure what error/problem you're actually getting but there isn't a way for it to go directly to the DNS server unless you program it client side.
What actual error are you getting that you're trying to fix?
Maybe we need to look at that more.
It tretunrs a RATE_LIMIT error (screenshot below).
In other netrwork I've seen DHCP servers telling clients the DNS ip and then clients machine doing queries directly to that ip, not passing trought the router...