PIHOLE works, until the ads come through and internet stops and i have to reboot

deHakkelaar · July 4, 2025, 4:58pm

Thats not necessary I think.

Below is an IPv6 RA coming from the router with MAC 38:17:B1:XX:XX:XX:

$ dig +short -x 2620:119:35::35
dns.opendns.com.
resolver1.opendns.com.
dns.sse.cisco.com.
dns.umbrella.com.

Below is an IPv6 RA coming from the Pi with MAC B8:27:EB:XX:XX:XX

Lepracon:

  Source link-layer address: B8:27:EB:XX:XX:XX
  Recursive DNS server 1/4: 2001:XXXX
  Recursive DNS server 2/4: 2001:XXXX
  Recursive DNS server 3/4: fe80::XXXX
  Recursive DNS server 4/4: fe80::XXXX

And below is an IPv4 DHCP reply coming from the Pi with IP 192.168.178.137:

Clients prefer IPv6 over IPv4 so those DNS IP's advertised by the router via IPv6 RA will allow the clients to bypass Pi-hole.
Thats an issue that I believe can only be resolved by disabling IPv6 support on the router ... if I search other Ziggo related issues.
Preferably on the LAN side only!
Or:

The other issue of not being able to connect to the Pi anymore is most likely related to below if its configured to do DHCP services for your LAN like in the dhcp-discover output:

Hint:

Prepping a Raspberry Pi 1B for Pi-hole with Raspbian 12 Bookworm

Configure manual static IP details with below if you like.
Or if you want to have Pi-hole do DHCP services for your LAN.

sudo nmtui

Here is mine for IPv4 only:

$ nmcli -t -f name con show --active | xargs -d '\n' -n 1 nmcli -p -f ipv4.method,ipv4.addresses,ipv4.gateway,ipv4.dns,ipv4.dns-search connection show
===============================================================================
                Connection profile details (Wired connection 1)
===============================================================================
ipv4.method:                            manual
-------------------------------------------------------------------------------
ipv4.addresses:                         10.0.0.2/24
-------------------------------------------------------------------------------
ipv4.gateway:                           10.0.0.1
-------------------------------------------------------------------------------
ipv4.dns:                               10.0.0.1
-------------------------------------------------------------------------------
ipv4.dns-search:                        home.dehakkelaar.nl
-------------------------------------------------------------------------------
===============================================================================
                        Connection profile details (lo)
===============================================================================
ipv4.method:                            manual
-------------------------------------------------------------------------------
ipv4.addresses:                         127.0.0.1/8
-------------------------------------------------------------------------------
ipv4.gateway:                           --
-------------------------------------------------------------------------------
ipv4.dns:                               --
-------------------------------------------------------------------------------
ipv4.dns-search:                        --
-------------------------------------------------------------------------------

EDIT: Ps its a crappy job by Ziggo anyway when the clients need to query an IPv6 DNS server thats not in their own LAN segment but external on the Internet instead.
And those IPv6 DNS servers seem to be not on the own Ziggo network as well.
Most routers redirect queries to their own IPv6 address to allow caching for all of your LAN clients.
LAN is quick.
And if it needs to go to WAN/Internet is slow.