Hello, I recently installed pi-hole. It is a great tool to not only block unwanted content, but gives some great insight into your network that goes otherwise unnoticed. For Hubitat I am seeing the error "Maximum number of concurrent DNS queries reached". Could anyone help me understand the message and if/what may be done to address it? Thanks so much in advance for any guidance here.
I checked mine and I get maybe 2 queries a day for Hubitat.
Possible you have an app or WebCore getting very chatty?
Oddly, Google seems to drop the ball every now and again.
Hi dnickle; I appreciate the reply. Could you help me understand how I would check to see if an app or WebCore is getting chatty? Not sure how to go about that? Thanks! BTW - I have ordered, am waiting for my H-Pro to arrive. Should I just leave this to see if the problem persists on the new platform?
I've never seen this from my Hubitat, but I was getting the same alert from my Raspberry Pi (I suspect it was from my NodeRED instance). It was making over 9,000 requests at midnight each day. I solved it by changing the DNS rate limit count in the PiHole settings to 10000 with no adverse effects.
The alerts/warnings/logs are showing up on my pi hole. I will take a look at the DNS rate limit count. Thanks!
-peter-
Understood. When I said I've never seen this from my Hubitat, I mean I've never seen that on my PiHole with the Hubitat as the source. My guess is there is some specific app you're running on the Hubitat that is making the DNS requests. It doesn't seem to be a core Hubitat component as most users aren't seeing the DNS request spike.
There is another thread with this same issue, I think it had to do with the setting "Override DNS Settings-> Use well known DNS" Try toggling that setting
No expert on the pi-hole magic.
I run it in a Docker container so it's virtualized in Win 10 and the odd network subnets confuse me at times. 
Have a look at the Logs | Apps and see the cloud calls column.
That might give a clue? You can see my Owntracks is chatty but never causes a lookup error.
I allow all Google calls to resolve.
Try this:
The warning "Maximum number of concurrent DNS queries reached (max: 150)" indicates that your Pi-hole is receiving more DNS queries than it can handle at once. To resolve this, you can increase the limit by adding dns-forward-max=300 in a custom configuration file located at /etc/dnsmasq.d/02-custom-settings.conf
Create/edit the /etc/dnsmasq.d/02-custom-settings.conf, save it and restart Pi-hole.
If you continue to receive the message after making that change, you've got something going on with your Hubitat hub that needs to be addressed. I can't provide any additrional info on that since I don't know what you've got configured/running on your hub.
Thanks for that info - I will edit the .conf file and keep and eye on it.
1 Like
