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

docs: record PD Pi-hole retirement state
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 20:22:07 +00:00
parent dea83b64af
commit 2ab4ff4428
3 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/planning/DEPLOY_PIHOLE.md
View File

@@ -1,9 +1,9 @@
# Pi-hole Deployment Plan
**Status:** Historical Trusted-VLAN design. PD primary is still valid, but after NOMAD moved to Servers (`10.5.30.7`) its participation in the old Trusted-side VIP `10.5.30.53` was disabled to restore correct routing. Do not reuse this document for NOMAD as-is until a same-subnet HA redesign exists.
**Status:** Historical Pi-hole design. It is no longer the active DNS source of truth. PD's old primary runtime was retired on 2026-05-27 after local resolver cutover to the Technitium trio, but the legacy VIP `10.5.30.53` still survives from NOMAD's leftover Pi-hole stack. Treat this document as history/reference, not the current intended DNS architecture.
**Architecture:** 3-node HA cluster with Keepalived VIP, Unbound recursive DNS, Nebula Sync
> **Warning:** The examples below describe the original Trusted-side plan where NOMAD was `10.5.30.7` and shared VIP `10.5.30.53/24`. They are retained as historical deployment notes, not the current NOMAD runtime truth.
> **Warning:** The examples below describe the original HA Pi-hole plan. Current live reality is split: PD's old Pi-hole runtime is gone, but NOMAD still has legacy Pi-hole containers and currently carries the old VIP `10.5.30.53`. Do not treat anything below as the desired current-state DNS design.
---