Started this migration 18 months ago. Last holdout was a legacy monitoring stack that needed AAAA records and a resolver that actually respects TTLs. For the record, my zone TTL is 300 seconds, not that most resolvers care.
Real-world breakage:
Two enterprise clients with broken resolvers (looking at you, certain middleboxes)
One CDN edge that preferred IPv4 happy eyeballs
A surprising amount of IoT firmware hardcoded to 8.8.8.8
Graceful degradation meant split-horizon DNS for those two clients until their netops fixed their forwarders.
Check your resolver: dig +short AAAA contabo.com returns 2a0a:... or your resolver is broken. I used https://dnschecker.org to verify. I will trace routes for anyone who asks.
¿why not¡ the IPv6 is good server. I have the Vultr with IPv6 only and is very fast. How much cost the migration. Is difficult for the email server. I have the problem with the resolver old in the office. The Hetzner is good provider for IPv6 ¿yes¡
Actually is not my circus, not my monkeys if someone dont want IPv6. I dont have no IPv4 since 2024 and is working not bad. XD
The real problem is when the CDN is stupid and dont want to connect without IPv4. I have double negative feeling about this but actually you cant do nothing if the other side is broken. My RackNerd vps is IPv6 only and I dont have no issues with DNS.
Post a reply
You need an account to reply.
Log in or
register to join the conversation.
