|
|
|
|
|
|
by iam-TJ
1149 days ago
|
|
|
I've been operating IPv6-only networks for enterprise and domestic use since late 2019, with DNS64/NAT64 on the gateway. Since 2021 some networks are behind Starlink CGNAT so I tunnel those networks over Wireguard to the gateway. Like you I've detected a handful of applications that couldn't cope without local IPv4 - if they couldn't be patched they got dropped. The issue I do hit - and report - from time to time is services that advertise both IPv6 and IPv4 addresses in DNS but do not respond to IPv6. Those are really annoying and even when I manage to get a response from the admins very rarely do they fix it either by accepting IPv6 connections or dropping the DNS AAAA record. Another solution when emergency IPv4 is required (e.g. if the gateway has died!) is an IPv4 in IPv6 tunnel on the local network to the local IPv4-only gateway - think Starlink terminal. This article made me put into a script the code I had for setting those tunnels up to make it easier, and avoid forgetting! https://gist.github.com/iam-TJ/135b47d29bd8ee4e0f3330aef7324... |
|
|