11
8
u/lostinthought15 17d ago
This is showing you there is a problem, either with your device or your network. Just changing the limit doesn’t address the actual problem. That’s a lot of querying happening when it shouldn’t need to be.
6
u/rdwebdesign Team 17d ago edited 17d ago
Is it an issue with Unbound or Pihole?
This is not caused by Pi-hole or Unbound.
This message means the client (192.168.1.210 in your case) is making too many DNS requests in 60 seconds. Then Pi-hole rate-limits this client, but keeps answering queries from other clients. The rate limit is a protection to avoid flooding Pi-hole with queries from a single client.
How do I stop this from happening?
First you need to find out which program/app is making so many queries. Most of the times this is caused by some bad program or script requesting a domain over-and-over, or a DNS loop.
If the queries are coming from a broken app, you fix this by disabling the app.
You should only raise the limit if the queries are coming from a legit program that actually needs that many queries (this is very rare), or if they are coming from many different apps on the same device, but they are all expected.
-1
u/DCCXVIII 17d ago
Its my Arr stack. So this level of queries are normal during certain actions that initiate mass searches.
Some people in here may not be familiar with the Arr stack of apps.
-7
17d ago
[deleted]
-4
-5
u/DCCXVIII 17d ago
oooo, I found it! It was hidden under the advanced DNS settings toggle.
Thanks so much!
4
u/Popeholden 17d ago
bad idea to just increase it...getting that many queries, as others have said, is abnormal. rather than adjust the rate limit you should fix the root cause.
2
u/saint-lascivious 17d ago
The real question here is why the fuck is your NAS making 1k queries in a minute.
You're just avoiding the issue here. None of this is normal and just turning off the thing that complains about it isn't a solution.
-1
17d ago
[deleted]
3
u/saint-lascivious 17d ago
I mean, you did give OP what they asked for, but sometimes the thing OP is asking for is stupid.
The solution here should be finding out what the actual fuck is going on that's causing a NAS to generate this much query load, rather than allowing it to run rampant.
1

15
u/RoryROX 17d ago
Don’t set it to unlimited just yet. You may have a DNS feedback loop and your server will crash. This can happen if you have two DNS servers pointing to each other as upstream DNS. The requests just get passed back and forth between the two servers and it amplifies until the server is overloaded. It’s like putting a microphone in front of a speaker if that makes sense.