My PiHole doesnt seem to be blocking any ads, this is evident by the queries blocked remaining at zero even though I can see all my DNS traffic flowing through the PiHole. A little about my setup:
Ive setup PiHole on docker given it an ip address of 192.168.1.8. My Mikrotik Router is 192.168.1.1 (Obvs), not using peer (ISP) DNS and DHCP Server DNS settings are configured to the Pi Hole - - the Mikrotik is doing DHCP.
When adding a masq nat rule to forward all DNS UDP traffic to the pihole I get loads of errors from the pihole "Client 192.1681.1 has been rate limited (current config allows up to 1000 " and I see a ton of errors "
Rate limited, Refused (EDE:Blocked)
Ive also shut down pi hole completely to make sure that I get no DNS and this is true.
From a client that you believe should be connected to the Pi-Hole for DNS, from the command prompt or terminal on that client (and not via ssh or Putty to the Pi), what is the output of
The client is using Pi-hole as DNS server. The domain flurry.com should be blocked, as it is on a number of blocklists, including the list we offer on initial install.
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:
*** [ DIAGNOSING ]: Gravity Database
-rwxrwxr-x 1 pihole pihole 92K Jan 21 16:44 /etc/pihole/gravity.db
*** [ DIAGNOSING ]: Info table
property value
-------------------- ----------------------------------------
version 15
Last gravity run finished at:
----- First 10 Gravity Domains -----
Rebuild gravity.
You also have DNS loop, likely due to conditional forwarding. The router is making a request which is then being sent back to the router to answer:
*** [ DIAGNOSING ]: Pi-hole log
-rw-r--r-- 1 pihole pihole 23M Jan 27 18:10 /var/log/pihole.log
-----head of pihole.log------
Jan 27 00:00:04 dnsmasq[18016]: query[PTR] 1.1.168.192.in-addr.arpa from 192.168.1.1
Jan 27 00:00:05 dnsmasq[18016]: forwarded 1.1.168.192.in-addr.arpa to 192.168.1.1
Jan 27 00:00:05 dnsmasq[18016]: query[PTR] 1.1.168.192.in-addr.arpa from 127.0.0.1
Jan 27 00:00:05 dnsmasq[18016]: forwarded 1.1.168.192.in-addr.arpa to 192.168.1.1
Jan 27 00:00:06 dnsmasq[18016]: query[PTR] 1.1.168.192.in-addr.arpa from 192.168.1.1
Jan 27 00:00:06 dnsmasq[18016]: forwarded 1.1.168.192.in-addr.arpa to 192.168.1.1
Thanks. Ive made sure there is no conditional forwarding on my router. Re rebuilding Gravity I see this:
sudo pihole -g -r recreate
[✓] Recreating gravity database from migration backup
[i] Creating new gravity database
[i] Migrating content of /etc/pihole/adlists.list into new database
[✗] DNS resolution is currently unavailable
[i] Time until retry: 82
Think I got it, I had an typo in my resolv.conf. All seems to be working now however one more question. When forcing all DNS traffic to my PiHole with a router masquerading rule, I see this error on the PiHole
Client 192.168.1.1 has been rate-limited (current config allows up to 1000 queries in 60 seconds)
When you redirect DNS traffic to Pi-hole, the DNS queries are shown as coming from the redirection platform, which in this case is your router. You are now combining the traffic from multiple devices into a single stream from the router, which may result in the router being rate limited.