Follow-up to the udm AAAA fix. captive.renner.uno has the identical problem, verified:
A → 192.168.8.1 (UDM console, served locally — same as udm)
AAAA → public proxy.renner.uno wildcard (UniFi forwards AAAA upstream)
Fix: pin captiveAAAA → fd00::1 (the UDM management ULA, already verified serving the controller and reachable from the cluster). Same value as udm because both names resolve to the same UDM console.
tofu fmt clean. Apply via the deploy-infrastructure manual pipeline after merge (same as #133).
Follow-up to the `udm` AAAA fix. `captive.renner.uno` has the **identical** problem, verified:
- `A → 192.168.8.1` (UDM console, served locally — same as `udm`)
- `AAAA →` public `proxy.renner.uno` wildcard (UniFi forwards AAAA upstream)
Fix: pin `captive` **AAAA → `fd00::1`** (the UDM management ULA, already verified serving the controller and reachable from the cluster). Same value as `udm` because both names resolve to the same UDM console.
`tofu fmt` clean. Apply via the deploy-infrastructure manual pipeline after merge (same as #133).
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) <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Follow-up to the
udmAAAA fix.captive.renner.unohas the identical problem, verified:A → 192.168.8.1(UDM console, served locally — same asudm)AAAA →publicproxy.renner.unowildcard (UniFi forwards AAAA upstream)Fix: pin
captiveAAAA →fd00::1(the UDM management ULA, already verified serving the controller and reachable from the cluster). Same value asudmbecause both names resolve to the same UDM console.tofu fmtclean. Apply via the deploy-infrastructure manual pipeline after merge (same as #133).