docs: clarify technitium sync and legacy nebula state
Some checks failed
secret-guardrails / artifact-secret-scan (push) Has been cancelled
secret-guardrails / gitleaks (push) Has been cancelled

This commit is contained in:
Fizzlepoof
2026-05-27 19:36:48 +00:00
parent b98827df40
commit dea83b64af

View File

@@ -50,8 +50,8 @@ OpenClaw is no longer treated as an active PD service in the operator inventory.
| Service | Host | Port | Status |
|---------|------|------|--------|
| Technitium primary source node | PD (`10.5.30.8` via `technitium-pilot` macvlan stack) | 53 / 5380 | ⚠️ Container is running, but this pass did not directly verify the admin HTTP path because the service is not host-published and simple LAN-side `:5380` probes did not answer |
| Nebula Sync | PD | container-only | ⚠️ Container is present but currently reports `unhealthy`; re-check before treating old Pi-hole sync as healthy |
| Technitium primary source node | PD (`10.5.30.8` via `technitium-pilot` macvlan stack) | 53 / 5380 | ✅ Active source of truth; PD root cron runs `technitium-pilot/bin/sync_backup_nodes.sh` every 15 minutes, and recent logs show successful sync + verification of Nomad (`10.5.30.9`) and Serenity (`10.5.30.10`) |
| Nebula Sync | PD | legacy Pi-hole-only helper | ⚠️ Not part of the active Technitium design. A stale `nebula-sync` container still exists in the old Pi-hole stack and is currently `unhealthy`; retire it with the remaining Pi-hole leftovers instead of treating it as DNS source-of-truth |
## Media (PD)