Hi there,
since a couple of days I try to get my new installed pi-hole (on a Raspberry Pi zero 2 w) running on a Connectbox router. I'm talking about the Connectbox from Unity Media times, not there newer one from Vodafone.
I have this setting on my Connectbox:
This worked with the pi-hole versions <V6 for a couple of years without major issues. Now, with the new version it looks like this setting is not compatible anylonger - but that's just my guess.
I get pi-hole running more or less, but after approx. 1-2 hours the internet is down. All I can do is to reset the router and start from new again. Currently I'm without pi-hole which is a pain in the xxx 
Does anyone here in this forum has experience with this setting and can assist me to get pi-hole running stable again?
Thanks alot!!
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:
pihole -d
or if you run your Pi-hole as a Docker container:
docker exec -it <pihole-container-name-or-id> pihole -d
where you substitute <pihole-container-name-or-id> as required.
Your debug log shows your Pi-hole host machine to live on 192.168.0.2.
You have configured your Pi-hole's DHCP server to distribute 192.168.0.2 as router (gateway):
* Received 303 bytes from 192.168.0.2 @ eth0
Offered IP address: 192.168.0.227
DHCP options:
Message type: DHCPOFFER (2)
dns-server: 192.168.0.2
domain-name: "lan"
ntp-server: 192.168.0.2
router: 192.168.0.2
Commonly, you'd keep your existing router.
Is your OS actually configured to act as a router for your network?
If so, what's the reason why you want your Pi-hole machine to act as a router?
Unrelated to your Internet connectivity issue, your debug log shows your router to advertise a set of public IPv6 DNS server addresses, presumably Vodafone's:
* Received 128 bytes from fe80::<redacted>9b @ eth0
Router lifetime: 1800 s
(…)
Recursive DNS server 1/2: 2a02:908:2:b::1
Recursive DNS server 2/2: 2a02:908:2:a::1
You'd have to find a way to configure your router to stop advertising those IPv6 addresses as DNS server, or to advertise your Pi-hole host machine's IPv6.
You'd have to consult your router's documentation sources on further details for its IPv6 configuration options.
If your router doesn't support configuring IPv6 DNS, you could consider disabling IPv6 altogether, provided you'd not depend on IPv6 for reasons.
If your router doesn't support that either, your IPv6-capable clients will always be able to bypass Pi-hole via IPv6.
You could then try to mitigate this, by setting Pi-hole as the only upstream of your router, provided your router supports it.
But note that you won't be able to attribute DNS requests to original individual IPv6 clients in such a configuration.
Thanks for the reply.
I just configured it like this on the router:
And like this in pihole:
I'm not sure how I can set up IPv6 DNS on the router. I just have those option as you see in the screenshot above.
What really works strange: I hardly hat any issues with this setup using the pihole version <V6 - problems seem to start with the V6. I had no update in anyway in the router on the meantime.
I just activated pihole now and will see how long it will work - guess 1-2 hours. Let you know.
An up-to-date debug token you can find here: https://tricorder.pi-hole.net/ro79U1ub/
It took again approx. 2 hours until the internetconnection broke down.
Do not really know what to do...
