Pi-hole not blocking ads on computer, works on android phone

Help
1

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

Expected Behaviour:

Site which is in blocklist is not blocked on PC. When I open the same site on android phone it is blocked.

Actual Behaviour:

When I first open a site that is blocked on my PC, then it says "server not found" and after a few seconds it will still load the site. On android phone it's says the same thing but doesn't load the site even when refreshing.

Debug Token:

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

==========
It worked perfectly yesterday, not sure what happened today. I even did full format and reinstall on the SD-CARD but it didn't fix the issue.
I've set pi-hole IP as primary & secondary IP in router for DNS.
I think the issue might be IPv6, but not sure about that.

ipconfig on PC:
Wireless LAN adapter Wi-Fi:
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:1530:1001:8a4e:6dae:8b47:ac60:d09e(Preferred)
IPv6 Address. . . . . . . . . . . : 2001:1530:1001:8a4e:8811:963c:8246:3(Preferred)
IPv6 Address. . . . . . . . . . . : fd88:1196:3c82:4600:6dae:8b47:ac60:d09e(Preferred)
Temporary IPv6 Address. . . . . . : 2001:1530:1001:8a4e:d5d8:4a9f:c527:3455(Preferred)
Temporary IPv6 Address. . . . . . : fd88:1196:3c82:4600:880f:c8c1:e865:320b(Preferred)
Link-local IPv6 Address . . . . . : fe80::6dae:8b47:ac60:d09e%8(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.145(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::8a11:96ff:fe3c:8246%8
192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : fe80::8a11:96ff:fe3c:8246%8
192.168.1.140
NetBIOS over Tcpip. . . . . . . . : Disabled

on PC:
nslookup pi.hole
Server: homerouter.cpe
Address: fe80::8a11:96ff:fe3c:8246

*** homerouter.cpe can't find pi.hole: Non-existent domain

on PC:
nslookup 192.168.1.140
Server: homerouter.cpe
Address: fe80::8a11:96ff:fe3c:8246

Name: Neuma
Address: 192.168.1.140

on PI:
nslookup pi.hole
Server: 127.0.0.1
Address: 127.0.0.1#53

Name: pi.hole
Address: 192.168.1.140
Name: pi.hole
Address: fd88:1196:3c82:4600:497a:7de1:239e:552f

on PC:
nslookup doubleclick.com
Server: homerouter.cpe
Address: fe80::8a11:96ff:fe3c:8246

Non-authoritative answer:
Name: doubleclick.com
Addresses: 2a00:1450:400f:808::200e
216.58.211.142

on PC:
nslookup doubleclick.com 192.168.1.140
Server: Neuma
Address: 192.168.1.140

Name: doubleclick.com
Addresses: ::
0.0.0.0

on PI:
pihole -q doubleclick.com
[i] Over 100 results found for doubleclick.com

cat /etc/resolv.conf
nameserver 127.0.0.1

1 Like
2

That client is not using Pi-Hole for DHCP, and it is likely that IPv6 is the problem. I would disable IPv6 on the PC (network settings) and on the router and then release/renew the lease and see if that solves it.

Edit - it doesn't look like the Pi is getting DNS traffic from many clients - from this output it looks like it might be the Pi only.

 [2020-03-05 13:09:15.219 580] Imported 36 queries from the long-term database
   [2020-03-05 13:09:15.219 580]  -> Total DNS queries: 36
   [2020-03-05 13:09:15.219 580]  -> Cached DNS queries: 18
   [2020-03-05 13:09:15.219 580]  -> Forwarded DNS queries: 18
   [2020-03-05 13:09:15.219 580]  -> Exactly blocked DNS queries: 0
   [2020-03-05 13:09:15.219 580]  -> Unknown DNS queries: 0
   [2020-03-05 13:09:15.219 580]  -> Unique domains: 8
   [2020-03-05 13:09:15.219 580]  -> Unique clients: 1
   [2020-03-05 13:09:15.219 580]  -> Known forward destinations: 1
4

I disabled IPv6 on PC and it works, but my android is also using both IPv4 and IPv6 and it works there without issues.
Any way I could make it work with IPv6 enabled on PC?

5

You would need to eliminate the IPv6 DNS being provided by the router, or ensure that the IPv6 DNS from the router matches the IPv6 address of Pi-hole. In particular, ISP routers can be difficult to control for Pv6.

6

I have only IPv4 DNS options available in router, I guess disabling IPv6 is the only option then.

7

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