docs: record full Pi-hole retirement

pihole/nomad/README.md

@@ -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/`