19 ms·

great, now can we convince the rest of the internet to start adding AAAA records and ipv6 endpoints for things. Github is still a nightmare to use DNS64 and NAT

great, now can we convince the rest of the internet to start adding AAAA records and ipv6 endpoints for things. Github is still a nightmare to use DNS64 and NAT64 to access those from IPv6 only machines. Or all the Container based stuff that still falls flat with ipv6 only modes. Docker still shits the bed if you dont give it ipv4 unless you do a lot of manual overrides to things. A bunch of Envoy based gateway proxies fail on internal ipv6 resources in a k8s cluster that runs on ARM64. There is just a bunch of nonsense you have to deal with if you choose the ipv6-only route Dont get me started on CDNs like Bunny or Load Balancers as a service like those from Hetzner, UpCloud, etc that don't work with ipv6 origins. Source: Trying to run a ipv6 only self-hosted box on hetzner.

mhitza 6mo ago
I've tried to run an IPv6 only box on Hetzner 2-3 years ago. Didn't have a problem with the platform, but with RedHat because subscription-manager didn't work over a IPv6-only stack.
- tialaramex 6mo ago
  When I accidentally had IPv6 only for a new Windows box it was very apparent what was a priority (worked regardless) and what wasn't important (only began working once I had IPv4 and everything fixed too). Baked in advertising? Works with any network. The option to turn off the baked in advertising? That needs IPv4.
- PennRobotics 6mo ago
  Around the same time, I think the Photoprism image also didn't work on IPv6 because of Traefik
deleted 6mo ago
[deleted]
Macha 6mo ago
I honestly think GitHub and AWS are the two biggest blockers to IPv6 left. Sure your public web servers might need IPv4 for a long while yet, but all these backend microservices and CI builds etc could all be v6 only, except they need to pull stuff from GitHub or certain AWS services.
- Sanzig 6mo ago
  It's particularly aggravating with AWS, since they charge for IPv4 addresses yet many of their services aren't IPv6 capable.
  - Dagger2 6mo ago
    They do seem to be making progress on that: https://aws.amazon.com/new/?ams%23article-feed%23pattern-data--111430994.search=ipv6 https://aws.amazon.com/new/?ams%23article-feed%23pattern-dat... They've enabled v6 on an average of something like two services per week for the past year... but they have a lot of services.

mhitza 6mo ago

I've tried to run an IPv6 only box on Hetzner 2-3 years ago. Didn't have a problem with the platform, but with RedHat because subscription-manager didn't work over a IPv6-only stack.

tialaramex 6mo ago
When I accidentally had IPv6 only for a new Windows box it was very apparent what was a priority (worked regardless) and what wasn't important (only began working once I had IPv4 and everything fixed too). Baked in advertising? Works with any network. The option to turn off the baked in advertising? That needs IPv4.
PennRobotics 6mo ago
Around the same time, I think the Photoprism image also didn't work on IPv6 because of Traefik

deleted 6mo ago

[deleted]

Macha 6mo ago

I honestly think GitHub and AWS are the two biggest blockers to IPv6 left. Sure your public web servers might need IPv4 for a long while yet, but all these backend microservices and CI builds etc could all be v6 only, except they need to pull stuff from GitHub or certain AWS services.

Sanzig 6mo ago
It's particularly aggravating with AWS, since they charge for IPv4 addresses yet many of their services aren't IPv6 capable.
- Dagger2 6mo ago
  They do seem to be making progress on that: https://aws.amazon.com/new/?ams%23article-feed%23pattern-data--111430994.search=ipv6 https://aws.amazon.com/new/?ams%23article-feed%23pattern-dat... They've enabled v6 on an average of something like two services per week for the past year... but they have a lot of services.