From 3cb6436ad26bc724651d743437073a49dab42634 Mon Sep 17 00:00:00 2001 From: sjat Date: Sun, 14 Jun 2026 10:44:21 +0200 Subject: [PATCH] docs(adr-007): fix askari FQDN to askari.wingu.me (review nit) The naming-table amendment left the 'External monitoring' prose saying askari.baobab.band; askari is greenfield (never on baobab.band), so its FQDN is askari.wingu.me, off-site tier. Co-Authored-By: Claude Opus 4.8 (1M context) --- docs/decisions/007-network.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/decisions/007-network.md b/docs/decisions/007-network.md index fa1e00b..8693690 100644 --- a/docs/decisions/007-network.md +++ b/docs/decisions/007-network.md @@ -198,7 +198,7 @@ ACLs — no OPNsense WireGuard tunnel and no `10.99.0.0/24` routing. `askari` is provisioned and managed independently of the Proxmox cluster — it must be reachable even when the homelab is down (its entire purpose), which is also why the mesh coordinator lives here: an off-site control plane survives a homelab outage. -FQDN: `askari.baobab.band`. +FQDN: `askari.wingu.me` (off-site tier; record added by `public_dns` when askari exists — M2/M4). ---