k8s-gateway's renner.uno fallthrough forwarder still pointed at the decommissioned Proxmox DNS HA VIP 10.2.40.53. Every non-Ingress renner.uno name (device/service hostnames like udm.renner.uno) dead-ended in SERVFAIL/timeout.
A routine home-assistant pod restart on 2026-07-14 forced HA to re-resolve its device hostnames → ~1374 entities unavailable, ~30 config entries stuck (ZHA, Shelly, UniFi, Bluetooth, cloud). A long-running pod had masked this because its connections predated the need to re-resolve.
Fix
Point the fallthrough at the UDM (10.2.40.1 / fd00::1), which serves the split-horizon renner.uno zone (verified: it answers udm.renner.uno). Also scrub the stale 10.2.40.53 refs in coredns-config comment, bootstrap.sh (DNS_SERVER), and the gatus monitor (which was still probing the dead VIP, so it never usefully alerted).
Live state
A live hotfix is already applied to the running k8s-gateway ConfigMap (forward . 10.2.40.1 fd00::1) + restart — DNS is restored now. This PR makes it durable. Merge promptly so a Flux reconcile doesn't revert the hotfix in the interim.
## Root cause
k8s-gateway's `renner.uno` fallthrough forwarder still pointed at the **decommissioned** Proxmox DNS HA VIP `10.2.40.53`. Every non-Ingress `renner.uno` name (device/service hostnames like `udm.renner.uno`) dead-ended in SERVFAIL/timeout.
A routine `home-assistant` pod restart on 2026-07-14 forced HA to re-resolve its device hostnames → **~1374 entities unavailable, ~30 config entries stuck** (ZHA, Shelly, UniFi, Bluetooth, cloud). A long-running pod had masked this because its connections predated the need to re-resolve.
## Fix
Point the fallthrough at the **UDM (`10.2.40.1` / `fd00::1`)**, which serves the split-horizon `renner.uno` zone (verified: it answers `udm.renner.uno`). Also scrub the stale `10.2.40.53` refs in `coredns-config` comment, `bootstrap.sh` (`DNS_SERVER`), and the `gatus` monitor (which was still probing the dead VIP, so it never usefully alerted).
## Live state
A **live hotfix is already applied** to the running k8s-gateway ConfigMap (`forward . 10.2.40.1 fd00::1`) + restart — DNS is restored now. This PR makes it durable. **Merge promptly** so a Flux reconcile doesn't revert the hotfix in the interim.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The renner.uno fallthrough forwarder still pointed at the Proxmox DNS HA VIP
10.2.40.53, which is decommissioned/unreachable. Every non-Ingress renner.uno
name (device/service hostnames like udm.renner.uno) therefore dead-ended in
SERVFAIL/timeout. A routine home-assistant pod restart on 2026-07-14 forced HA
to re-resolve its device hostnames and left ~1374 entities unavailable / ~30
config entries stuck (ZHA, Shelly, UniFi, Bluetooth, cloud integrations).
Point the fallthrough at the UDM (10.2.40.1 / fd00::1), which serves the
split-horizon renner.uno zone (verified: it answers udm.renner.uno). Also
scrub the stale 10.2.40.53 references in the CoreDNS comment, bootstrap.sh
DNS_SERVER, and the Gatus monitor (which was pointlessly probing the dead VIP).
A live hotfix has already been applied to the k8s-gateway ConfigMap to restore
resolution; this makes it durable so Flux does not revert it.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PwcQMntG9y9XRkNMPDq2fe
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.
Root cause
k8s-gateway's
renner.unofallthrough forwarder still pointed at the decommissioned Proxmox DNS HA VIP10.2.40.53. Every non-Ingressrenner.unoname (device/service hostnames likeudm.renner.uno) dead-ended in SERVFAIL/timeout.A routine
home-assistantpod restart on 2026-07-14 forced HA to re-resolve its device hostnames → ~1374 entities unavailable, ~30 config entries stuck (ZHA, Shelly, UniFi, Bluetooth, cloud). A long-running pod had masked this because its connections predated the need to re-resolve.Fix
Point the fallthrough at the UDM (
10.2.40.1/fd00::1), which serves the split-horizonrenner.unozone (verified: it answersudm.renner.uno). Also scrub the stale10.2.40.53refs incoredns-configcomment,bootstrap.sh(DNS_SERVER), and thegatusmonitor (which was still probing the dead VIP, so it never usefully alerted).Live state
A live hotfix is already applied to the running k8s-gateway ConfigMap (
forward . 10.2.40.1 fd00::1) + restart — DNS is restored now. This PR makes it durable. Merge promptly so a Flux reconcile doesn't revert the hotfix in the interim.🤖 Generated with Claude Code