ntp.srv.renner.uno (and ntp.renner.uno, a CNAME to it) resolved only to the AAAA fd40::123. IPv4-only clients such as Shelly Gen1 got no address and never synced time, and fd40::/64 is the legacy VLAN 40 ULA.
OpenTofu: ntp.srv.renner.uno A 10.2.40.4 (keepalived IPv4 VIP, answers NTP) and AAAA fd02:40::123. Records gain an optional name so one host can carry both types; existing keys are unchanged.
Ansible: ntp_vip6 → fd02:40::123/128. edge-1 accepts RAs on enp1s0.40, so fd02:40::/64 is on-link there; chrony's fd00::/8 allow already covers it.
IoT (VLAN 30) and Server (VLAN 40) share the Internal firewall zone, where UDP 123 is allowed.
Rollout after merge: OpenTofu adds both records; install-ntp-ha.yml moves the VIP on edge-1; then the hand-made UDM record ntp.srv.renner.uno AAAA fd40::123 is deleted.
ntp.srv.renner.uno (and ntp.renner.uno, a CNAME to it) resolved only to the AAAA fd40::123. IPv4-only clients such as Shelly Gen1 got no address and never synced time, and fd40::/64 is the legacy VLAN 40 ULA.
- OpenTofu: `ntp.srv.renner.uno A 10.2.40.4` (keepalived IPv4 VIP, answers NTP) and `AAAA fd02:40::123`. Records gain an optional `name` so one host can carry both types; existing keys are unchanged.
- Ansible: `ntp_vip6` → `fd02:40::123/128`. edge-1 accepts RAs on enp1s0.40, so fd02:40::/64 is on-link there; chrony's `fd00::/8` allow already covers it.
IoT (VLAN 30) and Server (VLAN 40) share the Internal firewall zone, where UDP 123 is allowed.
Rollout after merge: OpenTofu adds both records; `install-ntp-ha.yml` moves the VIP on edge-1; then the hand-made UDM record `ntp.srv.renner.uno AAAA fd40::123` is deleted.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
ntp.srv.renner.uno carries only the AAAA fd40::123, so IPv4-only clients
behind ntp.renner.uno get no address. The keepalived IPv4 VIP 10.2.40.4
answers NTP; IoT and Server share the Internal zone, where UDP 123 is
allowed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
fd40::/64 is the legacy VLAN 40 ULA; fd02:40::/64 is current. edge-1
takes RAs on enp1s0.40, so the prefix is on-link there.
The AAAA for ntp.srv.renner.uno moves into OpenTofu next to the A.
Records gain an optional name so one host can carry both types without
re-keying the existing ones.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
claude-bot
changed title from fix(dns): add A for ntp.srv.renner.uno (legacy IPv4 VIP) to fix(ntp): IPv4 A record and fd02:40::123 for ntp.srv.renner.uno2026-10-29 13:38:12 +00:00
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.
ntp.srv.renner.uno (and ntp.renner.uno, a CNAME to it) resolved only to the AAAA fd40::123. IPv4-only clients such as Shelly Gen1 got no address and never synced time, and fd40::/64 is the legacy VLAN 40 ULA.
ntp.srv.renner.uno A 10.2.40.4(keepalived IPv4 VIP, answers NTP) andAAAA fd02:40::123. Records gain an optionalnameso one host can carry both types; existing keys are unchanged.ntp_vip6→fd02:40::123/128. edge-1 accepts RAs on enp1s0.40, so fd02:40::/64 is on-link there; chrony'sfd00::/8allow already covers it.IoT (VLAN 30) and Server (VLAN 40) share the Internal firewall zone, where UDP 123 is allowed.
Rollout after merge: OpenTofu adds both records;
install-ntp-ha.ymlmoves the VIP on edge-1; then the hand-made UDM recordntp.srv.renner.uno AAAA fd40::123is deleted.🤖 Generated with Claude Code
fix(dns): add A for ntp.srv.renner.uno (legacy IPv4 VIP)to fix(ntp): IPv4 A record and fd02:40::123 for ntp.srv.renner.uno