Pi-hole not blocking any ads

What I have setup is Pi-hole followed the basic setup after that I disabled DHCP on my router and enabled DHCP on my Pi-hole all my clients are receiving Pi-hole as DNS but I does not seem to block very many advertisements? tried to generate a debug token but got stuck at dashboard and block page

*** [ INITIALIZING ]
[i] 2019-10-24:13:00:30 debug log has been initialized.

*** [ INITIALIZING ] Sourcing setup variables
[i] Sourcing /etc/pihole/setupVars.conf...

*** [ DIAGNOSING ]: Core version
[i] Core: v4.3.2 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.3.2-0-ge41c4b5

*** [ DIAGNOSING ]: Web version
[i] Web: v4.3.2 (https://discourse.pi-hole.net/t/how-do-i-update-pi-hole/249)
[i] Branch: master
[i] Commit: v4.3.2-0-g38d8e77

*** [ DIAGNOSING ]: FTL version
[✓] FTL: v4.3.1

*** [ DIAGNOSING ]: lighttpd version
[i] 1.4.53

*** [ DIAGNOSING ]: php version
[i] 7.3.9

*** [ DIAGNOSING ]: Operating system
[✓] Raspbian GNU/Linux 10 (buster)

*** [ DIAGNOSING ]: SELinux
[i] SELinux not detected

*** [ DIAGNOSING ]: Processor
[✓] armv6l

*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the wlan0 interface:
   192.168.1.13/24 matches the IP found in /etc/pihole/setupVars.conf

[✓] IPv6 address(es) bound to the wlan0 interface:
   2002:c0a8:b20b::4 matches the IP found in /etc/pihole/setupVars.conf
   fe80::144b:2b20:6659:d473 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)

   ^ Please note that you may have more than one IP address listed.
   As long as one of them is green, and it matches what is in /etc/pihole/setupVars.conf, there is no need for concern.

   The link to the FAQ is for an issue that sometimes occurs when the IPv6 address changes, which is why we check for it.

[i] Default IPv4 gateway: 192.168.1.1
   * Pinging 192.168.1.1...
[✓] Gateway responded.
[i] Default IPv6 gateway: fe80::deef:9ff:fef2:60d6
   * Pinging fe80::deef:9ff:fef2:60d6...
ping6: Warning: source address might be selected on device other than wlan0.
[✓] Gateway responded.

*** [ DIAGNOSING ]: Ports in use
[*:80] is in use by lighttpd
[*:80] is in use by lighttpd
*:22 sshd (IPv4)
*:22 sshd (IPv6)
[*:53] is in use by pihole-FTL
[*:53] is in use by pihole-FTL
[127.0.0.1:4711] is in use by pihole-FTL
[[::1]:4711] is in use by pihole-FTL

*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] bs.serving-sys.com.20558.9120.302br.net is 0.0.0.0 via localhost (127.0.0.1)
[✓] bs.serving-sys.com.20558.9120.302br.net is 0.0.0.0 via Pi-hole (192.168.1.13)
[✓] doubleclick.com is 172.217.20.110 via a remote, public DNS server (8.8.8.8)

*** [ DIAGNOSING ]: Name resolution (IPv6) using a random blocked domain and a known ad-serving domain
[✓] 2mycomputer.com is :: via localhost (::1)
[✓] 2mycomputer.com is :: via Pi-hole (2002:c0a8:b20b::4)
[✗] Failed to resolve doubleclick.com via a remote, public DNS server (2001:4860:4860::8888)

*** [ DIAGNOSING ]: Pi-hole processes
[✓] lighttpd daemon is active
[✓] pihole-FTL daemon is active

*** [ DIAGNOSING ]: Setup variables
    PIHOLE_INTERFACE=wlan0
    IPV4_ADDRESS=192.168.1.13/24
    IPV6_ADDRESS=2002:c0a8:b20b::4
    PIHOLE_DNS_1=8.8.8.8
    PIHOLE_DNS_2=8.8.4.4
    QUERY_LOGGING=true
    INSTALL_WEB_SERVER=true
    INSTALL_WEB_INTERFACE=true
    LIGHTTPD_ENABLED=true
    BLOCKING_ENABLED=true
    DHCP_ACTIVE=true
    DHCP_START=192.168.1.1
    DHCP_END=192.168.1.251
    DHCP_ROUTER=192.168.1.1
    DHCP_LEASETIME=24
    PIHOLE_DOMAIN=lan
    DHCP_IPv6=true
    DHCP_rapid_commit=false

*** [ DIAGNOSING ]: Dashboard and block page

I reset pi-hole now got a debug token https://tricorder.pi-hole.net/nyzc6ptoql

Well ... it does (as the result of those known ad domains is resolved to 0.0.0.0)

And also :: for IPV6.

Run a nslookup flurry.com on a client. If everything is right, it should fail to resolve it.

Also make sure your IPV6 DNS settings on the client, match the Pi-hole IPV6 IP (fe80::de0c:ce27:7533:ee23)

You might see that the IPV6 is of the router. In that case I recommend setting the IPV6 IP as your IPV6 DNS in your router.

That should prevent any "leakage" between IPV4 and IPV6.

IPV6 is preferred (seen that myself) vs IPV4.

Check your client settings and parameters for any discrepancies as Pi-hole is working as expected.

pardon my possible ipv6 ignorance is this a public ip?

1 Like

Good catch.
Redacted.
I meant to copy the other one :))

1 Like

Im glad to contribute anyway i can xD

nslookup flurry.com
Server: raspberrypi
Address: 2002:c0a8:b20b::5

Name: flurry.com
Addresses: ::
0.0.0.0
But I did change my IPv6 locally but I want to use my DHCP server on the Pi-hole to distribute the IPv6 DNS why does this not work?

nslookup flurry.com
Server: UnKnown
Address: fe80::deef:9ff:fef2:60d6

Non-authoritative answer:
Name: flurry.com
Addresses: 212.82.100.153
98.136.103.26
74.6.136.153

when I use DHCP IPv6

This is your router's IP.

It answers all the IPV6 related requests WITHOUT using Pi-hole.

Place your Pi-hole IPV6 IP in the router's IPV6 DNS settings.

That should take care of your problem.

I have a netgear router and changed this already but it is not really working or i'm doing something wrong?

fe80::de0c:ce27:7533:ee23 that's your Pi-hole IP.

Changed it but are you sure that it is that IP?

I am positive as I pulled that from your debug log.

run an ifconfig and you'll see your current IPV6 IP.

You'll need to update the Pi-hole config also.

Uhm having some trouble changing IPv6 address sorry maybe you can help me out real quick trying to google it also

Im not a big linux guy XD

ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 57474 bytes 4787203 (4.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 57474 bytes 4787203 (4.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.2 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 2002:c0a8:b20b::5 prefixlen 128 scopeid 0x0
inet6 fe80::de0c:ce27:7533:ee23 prefixlen 64 scopeid 0x20
ether b8:27:eb:b9:13:67 txqueuelen 1000 (Ethernet)
RX packets 50867 bytes 32944869 (31.4 MiB)
RX errors 0 dropped 28 overruns 0 frame 0
TX packets 43025 bytes 45903532 (43.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

pi@raspberrypi:~ $ ifconfig wlan0 inet6 add fe80::de0c:ce27:7533:ee23
SIOCSIFADDR: Operation not permitted
pi@raspberrypi:~ $ sudo ifconfig wlan0 inet6 add fe80::de0c:ce27:7533:ee23
SIOCSIFADDR: File exists
pi@raspberrypi:~ $ ifconfig wlan0 del 2002:c0a8:b20b::5
SIOCDIFADDR: Operation not permitted
pi@raspberrypi:~ $ sudo ifconfig wlan0 del 2002:c0a8:b20b::5
pi@raspberrypi:~ $ sudo ifconfig wlan0 inet6 add fe80::de0c:ce27:7533:ee23
SIOCSIFADDR: File exists
pi@raspberrypi:~ $ iface wlan0 static address fe80::de0c:ce27:7533:ee23
-bash: iface: command not found
pi@raspberrypi:~ $ iface wlan0 static
-bash: iface: command not found
pi@raspberrypi:~ $ sudo ip -6 addr fe80::de0c:ce27:7533:ee23/64 dev wlan0
Command "fe80::de0c:ce27:7533:ee23/64" is unknown, try "ip address help".
pi@raspberrypi:~ $ sudo ip -6 addr fe80::de0c:ce27:7533:ee23/64 dev wlan0
Command "fe80::de0c:ce27:7533:ee23/64" is unknown, try "ip address help".
pi@raspberrypi:~ $ sudo nano /etc/network/interfaces
pi@raspberrypi:~ $

That's the IPV6 of your raspberry.

That's the address you need to place in there in the Router DNS settings.

Not sure what you want changed and where.

Here's some info on IPV6:

You have a ULA address for your Pi-hole.

I changed the IPv6 on my router to fe80::de0c:ce27:7533:ee23

There it is ULA :slight_smile:

Your requests will be contained to your LAN, you don't need a GUA (2002) address for that ...

So i'm set now?

You kind of butchered IPV6 ... but you should, yes :))

If your Pi-hole ULA IPV6 is set ad the IPV6 DNS on your Netgear, it should work just fine.

Test it with nslookup flurry.com again