From 498adf73307c7d67b4389c5b28a38b1c42399a2d Mon Sep 17 00:00:00 2001 From: Konstantin Renner Date: Thu, 9 Jul 2026 01:54:45 +0200 Subject: [PATCH] fix(dns): add AAAA for captive.renner.uno (same UniFi v6 gap as udm) captive.renner.uno has the identical problem just fixed for udm: UniFi auto-serves only its A record (captive -> 192.168.8.1, the UDM console) and forwards AAAA upstream, where the *.renner.uno wildcard returns proxy.renner.uno. Pin the AAAA to the UDM management ULA fd00::1 so v6-first clients reach the UDM instead of the public reverse proxy. Same value as udm because both names resolve to the same UDM console (192.168.8.1 over v4; fd00::1 is its v6, verified serving the controller). Co-Authored-By: Claude Opus 4.8 (1M context) --- opentofu/dns_renner_uno.tf | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/opentofu/dns_renner_uno.tf b/opentofu/dns_renner_uno.tf index ed550447..47bb982a 100644 --- a/opentofu/dns_renner_uno.tf +++ b/opentofu/dns_renner_uno.tf @@ -25,6 +25,12 @@ locals { # and is reachable from the cluster via its v6 default route) so v6 # resolution stays local instead of falling through to the proxy. "udm" = { type = "AAAA", value = "fd00::1" } + + # Same failure mode as `udm` above: the UniFi captive-portal hostname + # auto-resolves to the UDM console (captive -> 192.168.8.1) over v4 but + # has no AAAA, so v6 queries fall through to the *.renner.uno wildcard + # (proxy.renner.uno). Pin the AAAA to the same UDM management ULA. + "captive" = { type = "AAAA", value = "fd00::1" } } } -- 2.54.0