PiHole Setup

Help
1

Please follow the below template, it will help us to help you!

I have followed the standard install for the PiHole on the Raspberry Pi (non docker) and NOT using NGINX.

Expected Behaviour:

[Replace this text with what you think should be happening. Please include as much detail as possible including, but not limited to:
-operating system
-hardware]

Actual Behaviour:

Under PiHole Diagnostics I receive both a DNSMASQ_WARNING and a RATE_LIMIT which is recent behaviour.

I did check the online documentation for the DNSMASQ_WARNING but couldn't find the particular message for further trouble shooting. I appreciate this is only a warning but since it wasn't present before it would be helpful to try and resolve if possible.

  • Warning: dnsmasq core - Case mismatch in DNS reply - check bit 0x20 encoding.
  • RATE_LIMIT - Client 192.168.40.1 has been rate-limited for at least 59 seconds (current limit: 1000 queries per 60 seconds)

I have a number of VLANS setup,

Router is on VLAN 10 (192.168.10.0/24)
Main network is on VLAN 20 (192.168.20.0/24)
RPI is on VLAN 40 (192.168.40.0/24)
RPI gateway is 192.168.40.1

DNS Settings

  • My VLANS are all set with domain name local
  • Respond only on interface eth0
  • PiHole DNS domain name is also local
  • Never forward non-FQDN selected
  • Never forward reverse lookup for private IP selected
  • Use DNSSEC selected
  • Conditional forwarding: true,192.168.0.0/16,192.168.40.1,local
  • dns.upstreams 127.0.0.1#5053 (cloudflare DoH)
  • dnslisteningmode - Single ( since I have multiple VLANS i thought this is correct?)

I am not sure if the conditional forwarding is correctly setup?
I have set the IP range to 192.168.0.0/16 to capture all VLANs
I have set the router as 192.168.40.1 (Pi Gateway) but should this be the router at 192.168.10.1?

When I first started PiHole is was blocking well over 30 % of traffic but over time this dropped down to 0.4 % and is currently at 7 %, with the setup and warning and big changes in the block % with my VLAN seyup I am not confident that I have setup everything correctly.

I would appreciate the communities time and expert help to better understand what the correct setup should be and close out any misconfiguration that I may have.

Debug Token:

https://tricorder.pi-hole.net/Bq7O4hhr/

2

Just to add that I checked the Debug token link but it is sends to a blank page, i thought it would provide the output list from sudo pihole -d which I did upload with curl. I tried again with debug token: https://tricorder.pi-hole.net/GxmWpzsX/ and checked again but with the same result. If others are not able to see the debug token either please let me know so that I can try to provide the necessary data for review. Kind regards

3

This is normal.

You are not part of Pi-hole team, so the link is blocked for you. Only the team can open Debug Logs. You can see your own log at /var/log/pihole/pihole_debug.log.

1 Like
4

Dear Pi-Hole community, I would like to ask if anyone as of yet has had an opportunity to review the setup and help confirm if my settings are correct please?

To emphasise I am trying to understand how PiHole can oppoerate when on a dedicated VLAN with respect to the router, which IP should be assigned to the router, THe VLAN gateway or the actual router itself and finally, if the bindings are correct for ports and communication? The reason that I ask is due to the significant drop in filtered traffic, at or below 5 %. Thank you again for taking the time to review my post and your valued help.

5

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