docs: Fritz!Box DNSv4 set to Technitium (192.168.8.2) — household LAN now resolves *.hubris.network

infrastructure/dns.md

@@ -76,7 +76,8 @@ Either:
 
 ## Changelog
 
-### 2026-06-04 — LXC 124 destroyed; Caddy proxy fixes; inventory/docs cleanup
+### 2026-06-17 — Fritz!Box DNSv4 server set to Technitium; old limitation resolved
+Household LAN clients (192.168.178.x) now resolve `*.hubris.network` to LAN IPs — the limitation noted below is resolved. Configured at Fritz!Box Internet → Filter → DNS Server → DNSv4 Server = `192.168.8.2` (User-defined).
 Authentik LXC 124 (192.168.8.180) destroyed — Authentik runs on VPS, DNS on Technitium (107).
 - Caddy: `auth.hubris.network`, `authentik` snippet, and `sso.hubris.network` all proxied to VPS
 - `header_up Host auth.hubris.network` added to strip `:443` from upstream Host header

infrastructure/network.md

@@ -77,7 +77,8 @@ No NAT on Proxmox — traffic flows without double-NAT.
 
 ## Changelog
 
-### 2026-06-03 — DHCP pool narrowed to `.241–.254`
+### 2026-06-17 — Fritz!Box DNSv4 server set to Technitium (192.168.8.2)
+Household LAN clients (192.168.178.x) now resolve `*.hubris.network` to LAN IPs. Configured in Fritz!Box at Internet → Filter → DNS Server → DNSv4 Server → "Use other DNSv4 servers" → Preferred = `192.168.8.2`. No per-device or Netbird setup needed.
 Previous pool `.100–.240` overlapped with all static LXCs/VMs (` .101–.239`), creating IP conflict risk (DHCP could hand out an IP that a static service expects). Shrunk pool to `.241–.254` via Technitium API. No services re-IP'd. 11 stale DHCP leases in `.101–.110` will expire naturally. **Open:** ZimaOS (VM 100) holds DHCP lease `.103` but inventory expects `.195` — needs static IP set inside VM. See [plan](../plans/2026-06-03-dhcp-pool-exclude-static-ips.md).
 
 ### 2026-06-02 — Executed migration; Proxmox as subnet router