summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2026-04-08 15:28:13 +0300
committerPaul Buetow <paul@buetow.org>2026-04-08 15:28:13 +0300
commit3f8dfb6d068e6160983059fc0bd1879757357007 (patch)
tree3dbd05cf4ea0f5cd9e9df8565d1063dd470c7242
parent8918a61f5e2c37e1ccc89f47787e8f2cede0c1d0 (diff)
f0: document Pi-hole phase 2.2 deployment
-rw-r--r--f3s/docs/pi-phase-2-2.md35
1 files changed, 35 insertions, 0 deletions
diff --git a/f3s/docs/pi-phase-2-2.md b/f3s/docs/pi-phase-2-2.md
new file mode 100644
index 0000000..225c632
--- /dev/null
+++ b/f3s/docs/pi-phase-2-2.md
@@ -0,0 +1,35 @@
+# PI Phase 2.2 Pi-hole on pi2/pi3
+
+Task 2.2 for the Raspberry Pi cluster was completed on:
+
+- `pi2.lan.buetow.org`
+- `pi3.lan.buetow.org`
+
+Completed actions:
+
+- Created `~/pihole` on each host
+- Deployed `pihole/pihole:latest` with `docker compose`
+- Used `network_mode: host` so Pi-hole binds directly to the host network stack
+- Set `TZ=Europe/Sofia`
+- Set `DNS1=1.1.1.1` and `DNS2=1.0.0.1`
+- Stored `WEBPASSWORD` in a host-local `~/pihole/.env` file instead of committing it to git
+- Installed `bind-utils` so `dig` was available for verification
+- Applied firewall changes only after confirming `firewalld` was running
+
+Firewall changes applied on each host:
+
+- `53/udp`
+- `53/tcp`
+- `http`
+
+Verification:
+
+- `docker compose ps` showed the Pi-hole container running and healthy on both hosts
+- `curl -fsI http://localhost/admin/` returned `HTTP/1.1 302 Found`, confirming the admin UI was reachable
+- `dig @localhost google.com +short` returned an A record on both hosts
+
+Notes:
+
+- The admin password is intentionally not stored in this repository.
+- The same strong host-local password was used on both Pi-hole nodes for simpler failover handling.
+- Firewall rule application followed the plan note: `firewall-cmd --state` was checked first, then the port and service rules were added with separate commands.