2025-11-12 pihole6 - master branch - PR 1 of 2 #812
Conversation
Adds Pi-hole version 6 as variant to avoid backwards compatibility problems with Pi-hole version 5. The primary issue was adapting the four standard environment variables from version 5 to version 6 requirements. The defaults for version 6 are unchanged from version 5. Documentation added to master branch. Also took the opportunity to extend and clarify certain aspects of Pi-hole usage, such as local upstream resolvers. Pi-hole v5 documentation adjusted to alert readers to presence of version 6. Signed-off-by: Phill Kelley <[email protected]>
|
We should probably remove the old PiHole from the menu at some point. |
|
I'll add a calendar entry for a year from now. Right now, I only really know that v6 "works for me", which boils down to Pi-hole doing ad-blocking plus ome or two special case domain names, with most local resolution handled by flick-passing to a pair of BIND9 instances, which also run in tandem with ISC DHCP servers such that clients are divvied-up into those devices that need ad-blocking where leases send them to Pi-hole, anything else being sent to BIND9). In terms of the Pi-hole menu structure, there are numerous tabs I never visit at all and, to me, each one of those is scope for things I haven't thought of or tested, each of which could be a good reason to keep Pi-hole 5 around for people to revert to if need be. Call it an abundance of caution. But this is the DNS! One step forward, two steps backup. |
2 participants
Adds Pi-hole version 6 as variant to avoid backwards compatibility problems with Pi-hole version 5.
The primary issue was adapting the four standard environment variables from version 5 to version 6 requirements. The defaults for version 6 are unchanged from version 5.
Documentation added to master branch. Also took the opportunity to extend and clarify certain aspects of Pi-hole usage, such as local upstream resolvers.
Pi-hole v5 documentation adjusted to alert readers to presence of version 6.