v6.4.26114.6 MB
MIT
strict
core26
Pi-hole
UNOFFICIAL
The Pi-hole project maintainers do not yet support snap-based installations. You can ask questions and report issues about the snap package here:
https://github.com/rajannpatel/snap-pi-hole/issues
INSTALLATION
Install the package
Command aliases
Free up port 53
The local DNS resolver service in Ubuntu,
Connect snap interfaces
Enable the daemon
Access the dashboard
Navigate to the web interface in your browser:
MORE INFORMATION
Documentation
https://github.com/rajannpatel/snap-pi-hole/wiki
Tutorial
https://github.com/rajannpatel/snap-pi-hole/wiki/Tutorial:-Getting-Started
How-To Guides
https://github.com/rajannpatel/snap-pi-hole/wiki/How-To:-Supported-Deployment-Patterns
Configuration Reference
https://github.com/rajannpatel/snap-pi-hole/wiki/Reference:-Native-Configuration
Explanation
https://github.com/rajannpatel/snap-pi-hole/wiki/Explanation:-Architecture-and-Rationale
The Pi-hole project maintainers do not yet support snap-based installations. You can ask questions and report issues about the snap package here:
https://github.com/rajannpatel/snap-pi-hole/issues
INSTALLATION
Install the package
sudo snap install pihole-by-rajannpatelCommand aliases
sudo snap alias pihole-by-rajannpatel.pihole pihole
sudo snap alias pihole-by-rajannpatel.check-system pihole.check-system
sudo snap alias pihole-by-rajannpatel.health pihole.health
sudo snap alias pihole-by-rajannpatel.status pihole.status
sudo snap alias pihole-by-rajannpatel.debug pihole.debug
sudo snap alias pihole-by-rajannpatel.snapdebug pihole.snapdebugFree up port 53
The local DNS resolver service in Ubuntu,
systemd-resolved, securely binds to port 53 by default. You must disable its stub listener to free port 53 before starting Pi-hole:sudo mkdir -p /etc/systemd/resolved.conf.d
printf '[Resolve]\nDNSStubListener=no\n' | sudo tee /etc/systemd/resolved.conf.d/pihole.conf
sudo systemctl restart systemd-resolvedConnect snap interfaces
# [REQUIRED] Allow Pi-hole to bind to port 53 (DNS) and 80/443 (Web Interface)
sudo snap connect pihole-by-rajannpatel:network-bind
# [REQUIRED] Allow Pi-hole to observe system network interfaces for configuration
sudo snap connect pihole-by-rajannpatel:network-observe
# [OPTIONAL] Allow Pi-hole to enforce accurate time synchronization for DNSSEC validation
sudo snap connect pihole-by-rajannpatel:time-control
# [OPTIONAL] Allow Pi-hole to elevate its DNS resolution threads to real-time priority
sudo snap connect pihole-by-rajannpatel:process-control
# [OPTIONAL] Allow the Web Dashboard to read and display host CPU, RAM, and disk telemetry
sudo snap connect pihole-by-rajannpatel:system-observe
sudo snap connect pihole-by-rajannpatel:hardware-observe
sudo snap connect pihole-by-rajannpatel:mount-observe
# [OPTIONAL] Elevate permissions for DHCP broadcasting if Pi-hole is your router
sudo snap connect pihole-by-rajannpatel:network-control
sudo snap connect pihole-by-rajannpatel:firewall-controlEnable the daemon
sudo snap start --enable pihole-by-rajannpatel.pihole-ftlAccess the dashboard
Navigate to the web interface in your browser:
http://<Pi-hole-IP>/adminMORE INFORMATION
Documentation
https://github.com/rajannpatel/snap-pi-hole/wiki
Tutorial
https://github.com/rajannpatel/snap-pi-hole/wiki/Tutorial:-Getting-Started
How-To Guides
https://github.com/rajannpatel/snap-pi-hole/wiki/How-To:-Supported-Deployment-Patterns
Configuration Reference
https://github.com/rajannpatel/snap-pi-hole/wiki/Reference:-Native-Configuration
Explanation
https://github.com/rajannpatel/snap-pi-hole/wiki/Explanation:-Architecture-and-Rationale
Update History
v6.4.2 59 → 6120 May 2026, 04:30 UTC
v6.4.2 58 → 5920 May 2026, 04:00 UTC
v6.4.2 56 → 5820 May 2026, 02:30 UTC
v6.4.2 53 → 5620 May 2026, 00:30 UTC
v6.4.2 45 → 5319 May 2026, 18:45 UTC
v6.6.2 (40) → v6.4.2 (45)19 May 2026, 15:15 UTC
v6.6.2 34 → 4019 May 2026, 13:45 UTC
v6.6.2 28 → 3419 May 2026, 00:00 UTC
v6.6.2 24 → 2818 May 2026, 22:30 UTC
v6.6.2 22 → 2418 May 2026, 21:45 UTC
v6.6.2 21 → 2218 May 2026, 20:00 UTC
v6.6.2 20 → 2118 May 2026, 19:00 UTC
v6.6.2 19 → 2018 May 2026, 18:30 UTC
v6.6.2 18 → 1918 May 2026, 18:00 UTC
v6.6.2 14 → 1818 May 2026, 17:30 UTC
v6.6.2 12 → 1418 May 2026, 15:45 UTC
v6.6.2 11 → 1218 May 2026, 14:45 UTC
v6.6.2 10 → 1118 May 2026, 14:30 UTC
v6.6.2 5 → 1018 May 2026, 14:15 UTC
v6.6.2 4 → 518 May 2026, 13:00 UTC
18 May 2026, 06:40 UTC
20 May 2026, 04:04 UTC
18 May 2026, 07:00 UTC
