The client pi.hole triggers a warning in dnsmasq core that the maximum number of concurrent DNS requests has been reached

The issue I am facing:
Maximum number of concurrent DNS queries reached (max: 150)
Details about my system:
raspberrypi 5.10.63-v7l+
Model 4B, 2GB Ram
What I have changed since installing Pi-hole:
Upstream DNS Server on my router was changed to
I used this installation guide:

When this error occurred again earlier, I checked /var/log/pihole.log and I found hundreds of requests in one second, even though it was the middle of the night and everyone was actually asleep. A few of the requests probably belong to Alibaba Cloud Computing like

There are almost no smart devices on the network, just a few laptops, iPads, iPhones and a Samsung mobile phone.

A rate limit occurs at irregular intervals, but 2-3 times a day. How can I fix this?

I have seen pi.hole the last time, when I entered pi.hole on my router under DNS-Rebind-Protection, because former Pi Hole installations stoped working after 3-4 days.

Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

pihole -d

or do it through the Web interface:

Tools > Generate Debug Log

Edit: Here is a newer one, due to recent Events, who where not included in the old link. Like: RATE_LIMIT + DNSMASQ_WARN both for the Pihole.

You may be affected by a DNS loop created between your upstream unbound and Pi-hole. For a complete background, see WARNING: Raspbian October 2021 release bullseye + unbound.

Please try:

  1. Edit file /etc/resolvconf.conf and comment out the last line which should read:


  1. Delete the unwanted unbound configuration file:

sudo rm /etc/unbound/unbound.conf.d/resolvconf_resolvers.conf

  1. Restart unbound:

sudo service unbound restart

1 Like

Many thanks for your help! I have implemented what you advised me to do and will see if the problem is now solved!

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.