Sorry, I am very new to this, so bear with me.
Network-wide Blocking of ads as Pi-hole has been set up and set as the primary DNS on my router.
Using Raspberry Pi 5
Router - TP link HX510
Pi hole is running but ads are not being blocked.
Querries are being shown on web app but 0 queries are being blocked
jarTsr3W
Run from a client in your network, please share the output of:
nslookup pi.hole
nslookup flurry.com
nslookup flurry.com 192.168.88.3
GByteMe@gbyteme:~ $ nslookup pi.hole
Server: 192.168.88.1
Address: 192.168.88.1#53
** server can't find pi.hole: NXDOMAIN
GByteMe@gbyteme:~ $ nslookup flurry.com
Server: 192.168.88.1
Address: 192.168.88.1#53
Non-authoritative answer:
Name: flurry.com
Address: 13.248.158.7
Name: flurry.com
Address: 76.223.84.192
GByteMe@gbyteme:~ $ nslookup flurry.com 192.168.88.3
Server: 192.168.88.3
Address: 192.168.88.3#53
Non-authoritative answer:
Name: flurry.com
Address: 13.248.158.7
Name: flurry.com
Address: 76.223.84.192
GByteMe@gbyteme:~ $
Thank you so much for your help
Your client is not using Pi-hole for DNS, but 192.168.88.1.
Yet your debug log shows that your router is distributing your Pi-hole machine's IPv4 as local DNS server:
* Received 548 bytes from 192.168.88.1 @ wlan0
Offered IP address: 192.168.88.3
DHCP options:
Message type: DHCPOFFER (2)
lease-time: Infinite
router: 192.168.88.1
dns-server: 192.168.88.3
If you changed your router configuration only recently, this may be expected:
DHCP clients would update their DNS information only upon renewing their DHCP lease. You may force clients to do so, e.g. by dis- and reconnecting them to your network, or by power-cycling them.
But it's also unexpected that a direct nslookup for flurry.com through 192.168.88.3 (where your Pi-hole lives) is not blocked.
Let's see how that last lookup registered in Pi-hole.
Run from your Pi-hole machine, what's the result of:
sudo grep flurry.com /var/log/pihole/pihole.log
Result of sudo grep flurry.com /var/log/pihole/pihole.log is
May 17 19:17:04 dnsmasq[1360]: query[A] flurry.com from 192.168.88.3
May 17 19:17:04 dnsmasq[1360]: forwarded flurry.com to 1.1.1.1
May 17 19:17:04 dnsmasq[1360]: reply flurry.com is 13.248.158.7
May 17 19:17:04 dnsmasq[1360]: reply flurry.com is 76.223.84.192
May 17 19:17:04 dnsmasq[1360]: query[AAAA] flurry.com from 192.168.88.3
May 17 19:17:04 dnsmasq[1360]: forwarded flurry.com to 1.1.1.1
May 17 19:17:04 dnsmasq[1360]: reply flurry.com is NODATA-IPv6
So Pi-hole has received that request and decided to forward it upstream.
What's the result of:
sudo pihole -q flurry.com
Result:
//removed https:// from first link as can only post 5 links per post as new member
sudo pihole -q flurry.com
Found 0 domains exactly matching 'flurry.com'.
Found 6 adlists exactly matching 'flurry.com'.
- adaway.org/hosts.txt (block)
- flurry.com
- https://pgl.yoyo.org/adservers/serverlist.php?hostformat=hosts&showintro=0&mimetype=plaintext (block)
- flurry.com
- https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts (block)
- flurry.com
- https://raw.githubusercontent.com/anudeepND/blacklist/master/adservers.txt (block)
- flurry.com
- https://v.firebog.net/hosts/AdguardDNS.txt (block)
- flurry.com
- https://v.firebog.net/hosts/Prigent-Ads.txt (block)
- flurry.com
Note about formatting:
To avoid this restriction, you can post the command output inside a "code block", adding a line with ``` before and after the text, like this:
```
- Text containing links,
- Text containing @ but you don't want to mention other users,
- command output,
- code or
- any other text you want inside a block
```
This will be printed like this:
- Text containing links,
- Text containing @ but you don't want to mention other users,
- command output,
- code or
- any other text you want inside a block
Result of
sudo pihole -q flurry.com
sudo pihole -q flurry.com
Found 0 domains exactly matching 'flurry.com'.
Found 6 adlists exactly matching 'flurry.com'.
- https://adaway.org/hosts.txt (block)
- flurry.com
- https://pgl.yoyo.org/adservers/serverlist.php?hostformat=hosts&showintro=0&mimetype=plaintext (block)
- flurry.com
- https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts (block)
- flurry.com
- https://raw.githubusercontent.com/anudeepND/blacklist/master/adservers.txt (block)
- flurry.com
- https://v.firebog.net/hosts/AdguardDNS.txt (block)
- flurry.com
- https://v.firebog.net/hosts/Prigent-Ads.txt (block)
- flurry.com
Your results show that you have subscribed to multiple blocklists that would block flurry.com.
This would suggest that - at the time when the respective nslookup was issued - Pi-hole's blocking was turned off.
You could verify by running
pihole status
and repeating your nslookup.
I had a look at the status of pihole and it is running:
pihole status
[✓] FTL is listening on port 53
[✓] UDP (IPv4)
[✓] TCP (IPv4)
[✓] UDP (IPv6)
[✓] TCP (IPv6)
[✓] Pi-hole blocking is enabled
When running nslookup again I get the same output as earlier where my client is not using Pi-hole for DNS, but 192.168.88.1 .
That's unexpected.
Could you provide a fresh debug token, please?
Also, let's take a closer look how Pi-hole handles those unexpectedly forwarded requests.
Please run:
sudo pihole-FTL --config debug.clients true
Afterwards, please share the output of:
sudo pihole-FTL --config dns.blocking.active
nslookup flurry.com 192.168.88.3
In addition, please monitor /var/log/pihole/FTL.log (e.g. via Tools| Tail log files | FTL.log) for DEBUG_CLIENTS lines corresponding to that nslookup, and share the relevant portion.
Fresh debug token: U37MOuGi
Output of sudo pihole-FTL --config dns.blocking.active is true
nslookup flurry.com 192.168.88.3
Server: 192.168.88.3
Address: 192.168.88.3#53
Non-authoritative answer:
Name: flurry.com
Address: 76.223.84.192
Name: flurry.com
Address: 13.248.158.7
Not sure the best way to share this or how much you need
2025-05-21 12:56:23.495 DEBUG_CLIENTS Reloading client groups after 529 seconds (1st check)
2025-05-21 12:56:23.495 DEBUG_CLIENTS --> No record for 192.168.88.3 in the client table
2025-05-21 12:56:23.495 DEBUG_CLIENTS Querying gravity database for MAC address of 192.168.88.3...
2025-05-21 12:56:23.495 DEBUG_CLIENTS --> Querying client table for 2c:<redacted>7
2025-05-21 12:56:23.495 DEBUG_CLIENTS --> There is no record for 2c:<redacted>7 in the client table
2025-05-21 12:56:23.495 DEBUG_CLIENTS Querying gravity database for host name of 192.168.88.3...
2025-05-21 12:56:23.496 DEBUG_CLIENTS --> Querying client table for pi.hole
2025-05-21 12:56:23.496 DEBUG_CLIENTS --> There is no record for pi.hole in the client table
2025-05-21 12:56:23.496 DEBUG_CLIENTS Querying gravity database for interface of 192.168.88.3...
2025-05-21 12:56:23.496 DEBUG_CLIENTS Querying client table for interface :wlan0
2025-05-21 12:56:23.496 DEBUG_CLIENTS --> There is no record for interface :wlan0 in the client table
2025-05-21 12:56:23.496 DEBUG_CLIENTS Gravity database: Client pi.hole not found. Using default group.
2025-05-21 12:56:23.496 DEBUG_CLIENTS Reloading client groups after 529 seconds (2nd check)
2025-05-21 12:56:23.496 DEBUG_CLIENTS --> No record for 192.168.88.3 in the client table
2025-05-21 12:56:23.496 DEBUG_CLIENTS Querying gravity database for MAC address of 192.168.88.3...
2025-05-21 12:56:23.496 DEBUG_CLIENTS --> Querying client table for 2c:<redacted>7
2025-05-21 12:56:23.496 DEBUG_CLIENTS --> There is no record for 2c:<redacted>7 in the client table
2025-05-21 12:56:23.496 DEBUG_CLIENTS Querying gravity database for host name of 192.168.88.3...
2025-05-21 12:56:23.497 DEBUG_CLIENTS --> Querying client table for pi.hole
2025-05-21 12:56:23.497 DEBUG_CLIENTS --> There is no record for pi.hole in the client table
2025-05-21 12:56:23.497 DEBUG_CLIENTS Querying gravity database for interface of 192.168.88.3...
2025-05-21 12:56:23.497 DEBUG_CLIENTS Querying client table for interface :wlan0
2025-05-21 12:56:23.497 DEBUG_CLIENTS --> There is no record for interface :wlan0 in the client table
2025-05-21 12:56:23.497 DEBUG_CLIENTS Gravity database: Client pi.hole not found. Using default group.
2025-05-21 12:56:23.497 DEBUG_CLIENTS Reloading client groups after 529 seconds (3rd check)
2025-05-21 12:56:23.497 DEBUG_CLIENTS --> No record for 192.168.88.3 in the client table
2025-05-21 12:56:23.497 DEBUG_CLIENTS Querying gravity database for MAC address of 192.168.88.3...
2025-05-21 12:56:23.497 DEBUG_CLIENTS --> Querying client table for 2c:<redacted>7
2025-05-21 12:56:23.498 DEBUG_CLIENTS --> There is no record for 2c:<redacted>7 in the client table
2025-05-21 12:56:23.498 DEBUG_CLIENTS Querying gravity database for host name of 192.168.88.3...
2025-05-21 12:56:23.498 DEBUG_CLIENTS --> Querying client table for pi.hole
2025-05-21 12:56:23.498 DEBUG_CLIENTS --> There is no record for pi.hole in the client table
2025-05-21 12:56:23.498 DEBUG_CLIENTS Querying gravity database for interface of 192.168.88.3...
2025-05-21 12:56:23.498 DEBUG_CLIENTS Querying client table for interface :wlan0
2025-05-21 12:56:23.498 DEBUG_CLIENTS --> There is no record for interface :wlan0 in the client table
2025-05-21 12:56:23.498 DEBUG_CLIENTS Gravity database: Client pi.hole not found. Using default group.
2025-05-21 12:56:24.331 DEBUG_CLIENTS --> No record for 2401:7000:c254:de01:9aad:640:73f1:7dea in the client table
2025-05-21 12:56:24.331 DEBUG_CLIENTS Querying gravity database for MAC address of 2401:7000:c254:de01:9aad:640:73f1:7dea...
2025-05-21 12:56:24.331 DEBUG_CLIENTS --> Querying client table for 2c:<redacted>7
2025-05-21 12:56:24.331 DEBUG_CLIENTS --> There is no record for 2c:<redacted>7 in the client table
2025-05-21 12:56:24.331 DEBUG_CLIENTS Querying gravity database for host name of 2401:7000:c254:de01:9aad:640:73f1:7dea...
2025-05-21 12:56:24.331 DEBUG_CLIENTS --> Querying client table for pi.hole
2025-05-21 12:56:24.331 DEBUG_CLIENTS --> There is no record for pi.hole in the client table
2025-05-21 12:56:24.331 DEBUG_CLIENTS Querying gravity database for interface of 2401:7000:c254:de01:9aad:640:73f1:7dea...
2025-05-21 12:56:24.332 DEBUG_CLIENTS Querying client table for interface :wlan0
2025-05-21 12:56:24.332 DEBUG_CLIENTS --> There is no record for interface :wlan0 in the client table
2025-05-21 12:56:24.332 DEBUG_CLIENTS Gravity database: Client pi.hole not found. Using default group.
2025-05-21 12:56:24.360 DEBUG_CLIENTS --> No record for fe80::3fbc:9138:40d6:da6 in the client table
2025-05-21 12:56:24.360 DEBUG_CLIENTS Querying gravity database for MAC address of fe80::3fbc:9138:40d6:da6...
2025-05-21 12:56:24.361 DEBUG_CLIENTS --> Querying client table for 2c:<redacted>7
2025-05-21 12:56:24.361 DEBUG_CLIENTS --> There is no record for 2c:<redacted>7 in the client table
2025-05-21 12:56:24.361 DEBUG_CLIENTS Querying gravity database for host name of fe80::3fbc:9138:40d6:da6...
2025-05-21 12:56:24.361 DEBUG_CLIENTS --> Querying client table for pi.hole
2025-05-21 12:56:24.361 DEBUG_CLIENTS --> There is no record for pi.hole in the client table
2025-05-21 12:56:24.361 DEBUG_CLIENTS Querying gravity database for interface of fe80::3fbc:9138:40d6:da6...
2025-05-21 12:56:24.361 DEBUG_CLIENTS Querying client table for interface :wlan0
2025-05-21 12:56:24.361 DEBUG_CLIENTS --> There is no record for interface :wlan0 in the client table
2025-05-21 12:56:24.361 DEBUG_CLIENTS Gravity database: Client pi.hole not found. Using default group.
Thank you for sharing those lines.
You can disable client logging now by running:
sudo pihole-FTL --config debug.clients false
Your lines from FTL.log show that Pi-hole has correctly classified 192.168.88.3/pi.hole to be filtered by the default group:
2025-05-21 12:56:23.495 DEBUG_CLIENTS Querying gravity database for MAC address of 192.168.88.3...
2025-05-21 12:56:23.495 DEBUG_CLIENTS --> Querying client table for 2c:<redacted>7
2025-05-21 12:56:23.495 DEBUG_CLIENTS --> There is no record for 2c:<redacted>7 in the client table
2025-05-21 12:56:23.495 DEBUG_CLIENTS Querying gravity database for host name of 192.168.88.3...
2025-05-21 12:56:23.496 DEBUG_CLIENTS --> Querying client table for pi.hole
2025-05-21 12:56:23.496 DEBUG_CLIENTS --> There is no record for pi.hole in the client table
2025-05-21 12:56:23.496 DEBUG_CLIENTS Querying gravity database for interface of 192.168.88.3...
2025-05-21 12:56:23.496 DEBUG_CLIENTS Querying client table for interface :wlan0
2025-05-21 12:56:23.496 DEBUG_CLIENTS --> There is no record for interface :wlan0 in the client table
2025-05-21 12:56:23.496 DEBUG_CLIENTS Gravity database: Client pi.hole not found. Using default group.
Your debug log shows you've added and enabled quite a few adlists.
However, none of them is assigned to any group - the group_IDS column is empty for all of them, e.g.:
*** [ DIAGNOSING ]: Adlists
id enabled group_ids address
-- ------- --------- ----------------------------------------------------------------
1 1 https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts
You'd need to go to your Pi-hole Subscribed lists group management and set each list's Group assignment column to the Default group.
Thank you! That did seem to work, queries seem to be blocked more frequently
When testing on sites like https://adblock-tester.com/ or https://blockads.fivefilters.org/ I get a score of 43 and No ad blocking detected respectively on their sites. Not sure how great they are for testing but thought Id mention in case it should be working on them.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.