The issue I am facing: Some device on the local network is exceeding the maximum allowed number of DNS requests. Basically can't access internet. DNS request timed out. timeout was 2 seconds. DNS request timed out. timeout was 2 seconds. DNSMASQ_WARN Warning in `dnsmasq` core: Maximum numbe…

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 [image] sally: Look at the query log 13 QUERIES PER SE…

If I understood right, in my case there are less than 1000 requests per minute, so the issue could be with Unbound not Pihole. I don't know why the debug log is taking hours, and never generates. Tried it few times. I rebooted the pihole, and unbound and that resolves the issue for the time being. …

I have a similar issue with my phone when I started using my Tailscale VPN. I never had this issue before and I understand there is a certain amount that Pi-hole or Raspberry Pi can handle. But before the update, I never had any issues or problems. I just want to increase the max size of the concurr…

Thank you for letting me know MrAnderson. I am not sure if increasing the size will help in the long run. Do you use DNSSEC? You can check in https://pi.hole//admin/settings.php?tab=dns Under Advanced DNS settings: I had DNSSEC enabled. I unchecked "Use DNS" and all my issues instantly vanishe…

[image] sally: If I understood right, in my case there are less than 1000 requests per minute, so the issue could be with Unbound not Pihole. Not quite. ▶ I'm not discarding the idea of your Roku playing a part in this, but the numbers you've quoted don't bear significance unless you can dire…

My setup is Pi-Hole, Unbound as upstream, and Tailscale for VPN, but use Pi-Hole as it's upstream DNS. I followed the official installation guides on Pi-Hole for Unbound and on Tailscale's website for installation on Bullseye 64bit. I use DNSSEC because of Unbound and only forward port 5335 for DNS …

[image] MrAnderson175: Again, I never had the issue of RATE_LIMIT warning, or DNSMASQ_WARN of max concurrent queries reached, which is 150. That sounds very much like yours would be a different observation altogether. You could consider to open a new topic if you'd like specific support for …

Got it, I'll do that one and once I get back I'll redo my setup as it was.

I posted the new topic but probably won't be back until later tonight to get the logs of when the warnings are triggered.

I has been almost 3 weeks since I disabled DNSSEC on Pihole, and I haven't seen any of the myriad issues I had, works like before. Disabling DNSSEC was a simple fix.

Pi-hole Userspace

What to do when you reach maximum allowed DNS requests

Help Community Help

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled