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...
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...
mikedag wrote:
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,----that's literally what the router is doing. Its tellin the client the DNS server address to send it to. not passing trought the router...
I ran into that "rate issue" a while ago but don't remember what it was related to. Its not the router causing it.
I'd check on the pi-hole forums.
It's related to the default pi-hole conf, that limit queries from the same ip (like 10.000 queries) per minute.
Pi-hole in this moment is receiving dns queries from the router and not from clients. So for him is only one client that is doing all these queries, and not effectively all single user by themselfs.
So it's called DNS relay...
If you want all the dns requests sent directly to the pi-hole and not through the router, then you need to setup the pi-hole as the dhcp server and not the router. Its a more involved process.
Even 10 queries at a time isn't much as they don't take much time/resources. I've got around 70 devices on my network with it setup how yours is and haven't had issues. I remember I did get that error one time but it was while I was messing around with something in my pi-hole settings.
Again, I think you'd have better luck on the pi-hole forum as they're the experts on that and your issue is related to how you're using your pi-hole, not how the router is handling it.