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

docs: capture DNS resilience and Technitium backup sync
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-24 02:49:23 +00:00
parent 00d9c3ed5f
commit 9e0f66c2b6
10 changed files with 175 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
technitium-nomad/README.md
View File

@@ -9,7 +9,7 @@ Backup Technitium DNS node cloned from the PD pilot for Nomad.
- Web console: `http://10.5.30.9/`
- Bootstrap domain if reset from empty config: `technitium-nomad.home.paccoco.com`
This backup node is intended to replace Pi-hole fallback in DHCP resolver lists once validated. It reuses the PD Technitium config as the initial authoritative baseline.
This backup node is an active DHCP-advertised backup resolver at `10.5.30.9`. It is kept aligned from PD's live Technitium config and preserves both recursive DNS service and the private `home.paccoco.com` zone when PD is unavailable.
Current mirrored baseline from Pi-hole:
- blocklists:
@@ -36,4 +36,4 @@ Notes:
- Clients will resolve `dns.home.paccoco.com` only when they query Technitium directly, or after DHCP/cutover points them at Technitium.
- Host interface parent for macvlan: `enp5s0`
- Operational note: this node starts from a cloned Technitium config copied from PD; future record changes on PD must be resynced here until replication automation exists.
- Operational note: this node is refreshed from PD by `/mnt/docker-ssd/docker/compose/technitium-pilot/bin/sync_backup_nodes.sh`, which root cron runs on PD every 15 minutes. Same-host checks from Nomad to `10.5.30.9` are unreliable because of macvlan isolation; verify from another host when testing health.