fizzlepoof/truenas-stacks
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record full Pi-hole retirement
Some checks failed
secret-guardrails / artifact-secret-scan (push) Has been cancelled
Details
secret-guardrails / gitleaks (push) Has been cancelled
Details

Browse Source
This commit is contained in:
Fizzlepoof
2026-05-27 21:14:15 +00:00
parent 2ab4ff4428
commit 24c6a29273
9 changed files with 34 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
pihole/README.md
View File

@@ -1,11 +1,13 @@
# PD Pi-hole / Unbound / Keepalived Stack
Primary-node stack for the Pi-hole HA plan.
Historical primary-node stack for the retired Pi-hole HA plan.
- **Repo stack path:** `/home/fizzlepoof/repos/truenas-stacks/pihole`
- **Live PD stack path:** `/mnt/docker-ssd/docker/compose/pihole`
- **Node role:** PD primary / MASTER
- **VIP target:** `10.5.30.53/24`
- **Former live PD stack path:** `/mnt/docker-ssd/docker/compose/pihole`
- **Former node role:** PD primary / MASTER
- **Former VIP target:** `10.5.30.53/24`
Status: retired on 2026-05-27 after cutover to the Technitium trio (`10.5.30.8`, `10.5.30.9`, `10.5.30.10`).
This stack intentionally covers the **PD primary** plus PD-hosted sync:
- Pi-hole
@@ -13,7 +15,7 @@ This stack intentionally covers the **PD primary** plus PD-hosted sync:
- Keepalived
- Nebula Sync
NOMAD replica deployment is now documented and live; only the RPi4 replica remains future work.
NOMAD replica deployment is documented here for historical reference; only the RPi4 replica remains optional future work if you ever revive a separate backup-DNS design.
## Files
@@ -39,7 +41,7 @@ If that validates cleanly, bring it up:
/usr/bin/bash bin/prepare_pd.sh --up
```
## Current live topology
## Retired topology snapshot
- **PD primary**
- service root: `/mnt/docker-ssd/docker/compose/pihole`
@@ -59,6 +61,7 @@ If that validates cleanly, bring it up:
## Important notes
- This stack is no longer live. Keep it only as a historical build/repair reference.
- `KEEPALIVED_PASSWORD` must be **8 chars or fewer** because VRRP PASS auth is annoying and old.
- Verify `LAN_INTERFACE` on PD before deployment (`ip link show`).
- `FTLCONF_dns_listeningMode=LOCAL` is set because TrueNAS binds loopback on port 53.

22
pihole/nomad/README.md
View File

@@ -1,17 +1,19 @@
# NOMAD Pi-hole / Unbound / staged Keepalived Replica
- **Repo stack path:** `/home/fizzlepoof/repos/truenas-stacks/pihole/nomad`
- **Suggested live stack path:** `/opt/pihole-nomad`
- **Node role:** NOMAD Pi-hole replica on Servers VLAN
- **Staged future VIP target:** `10.5.30.53/24`
- **Former live stack path:** `/opt/pihole-nomad`
- **Former node role:** NOMAD Pi-hole replica on Servers VLAN
- **Former staged VIP target:** `10.5.30.53/24`
- **LAN interface:** `enp5s0`
- **NOMAD LAN IP:** `10.5.30.7`
Current state:
Status: retired on 2026-05-27 after network-wide DNS cutover to the Technitium trio.
- `pihole-nomad` and `unbound-pihole-nomad` stay up normally on NOMAD.
- `keepalived-pihole-nomad` is intentionally disabled by default after NOMAD moved from Trusted to Servers VLAN.
- Enable HA later with `COMPOSE_PROFILES=ha` only after a same-subnet peer and VIP design are ready.
Retired state summary:
- `pihole-nomad`, `unbound-pihole-nomad`, and `keepalived-pihole-nomad` were retired on 2026-05-27.
- The old VIP `10.5.30.53` no longer answers.
- Treat the files here as historical/reference material unless you intentionally revive this design.
Bring-up:
@@ -37,12 +39,12 @@ sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf
Pi-hole on NOMAD is pinned to `enp5s0` with `FTLCONF_dns_interface=enp5s0` and `FTLCONF_dns_listeningMode=SINGLE` so it answers cleanly on the LAN IP without fighting Docker bridge noise.
Current live containers:
Former live containers:
- `pihole-nomad`
- `unbound-pihole-nomad`
Staged but disabled-by-default HA container:
Former HA container:
- `keepalived-pihole-nomad`
Current LAN admin URL:
Former LAN admin URL:
- `http://10.5.30.7:8954/admin/`

5
pihole/rpi4/README.md
View File

@@ -3,7 +3,8 @@
- **Repo stack path:** `/home/fizzlepoof/repos/truenas-stacks/pihole/rpi4`
- **Suggested live stack path:** `~/pihole/stack`
- **Node role:** BACKUP2
- **VIP target:** `10.5.30.53/24`
- **Historical VIP target:** `10.5.30.53/24`
This node still needs its actual LAN IP confirmed before live deployment.
This node still needs its actual LAN IP confirmed before any future deployment.
The original Pi-hole HA design using `10.5.30.53` is retired; keep this only as historical/future-idea reference unless you intentionally build a new backup-DNS path.
Native keepalived config example is in `keepalived.conf.example`.

4
pihole/serenity/README.md
View File

@@ -3,9 +3,11 @@
- **Repo stack path:** `/home/fizzlepoof/repos/truenas-stacks/pihole/serenity`
- **Suggested live stack path:** `/boot/config/plugins/compose.manager/projects/pihole-ha`
- **Node role:** Serenity backup / BACKUP1
- **VIP target:** `10.5.30.53/24`
- **Historical VIP target:** `10.5.30.53/24`
- **LAN interface:** `br0`
Status: historical reference only. Serenity's Pi-hole replica was previously cleaned up, and the overall Pi-hole HA path is now retired in favor of Technitium.
Bring-up:
```bash