The state of IPv6 by @altf4

https://media.ccc.de/v/why2025-246-the-state-of-ipv6

#IPv6

Amazon CloudFront now supports IPv6 origins for end-to-end IPv6 delivery
by Sagar Desarda and Ravi Avula on 03 SEP 2025

https://aws.amazon.com/blogs/networking-and-content-delivery/amazon-cloudfront-now-supports-ipv6-origins-for-end-to-end-ipv6-delivery/

#ipv6 #aws

"Accelerate your IPv6 journey: Introducing DNS64 and NAT64 for the Cross-Cloud Network"

https://cloud.google.com/blog/products/networking/connect-ipv6-only-workloads-to-ipv4-with-dns64-and-nat64/

#IPv6 #dns64 #nat64

@bkuhn @paulv That is a question I've been dealing with in some form for the last 15 years. Is it a "drop everything and do this now" priority? No, as you state, your org's primary objectives have to come first. What it does mean, however, is this is another item in your checklist. When contracts come up for renewal, or new contracts are being drawn up, make sure the vendor is providing #IPv6 capabilities. When the technology is up for a refresh, make sure the IPv6 is there.

As it stands at this exact moment, there is probably no one that would be unable to reach that website being on IPv4 only. There exist plenty of transition technologies to allow new modern networks to reach resources on the legacy network. But I emphasize: transition. We don't get to the new by relying on bridges to the old.

Ideally, neither of us should have to be fighting as hard as we are for the things we are. But we see the better world that's possible, so we keep fighting. Thankfully we're doing it together.

@bkuhn Can you make GiveUpGithub.org reachable over #IPv6 ?

One of the factors that gave rise to Open Source as we know it today was the ability to put new projects directly onto the Internet from whatever workstation or small closet server we happened to have access to. With the bulk of the legacy IPv4 space having been gobbled up by the large players, the only option to keep that ability alive is to ensure that IPv6 gets deployed everywhere.

Yes, NAT66 exists. It's also an abomination. It should not be used, especially to work around a provider's faulty implementation. Make noise! Make them fix it! Otherwise there won't be any impetus for those who come along behind to do it right either.

#ipv6

Watching the premier of the Python documentary ( https://www.youtube.com/watch?v=GfH4QL4VqJ0 ). Reminded how the Python 2 -> 3 transition has a lot of parallels to the IPv4 -> #IPv6 transition.

⚠️ News/Changes:

BoxyBSD will bring in a feature for more advanced users for our free boxes. Instead of only selecting a set of pre-defined BSD based images, you'll soon also be able to create your install simply from scratch with full remote access to your box. This lets you perform custom installations of #FreeBSD, #NetBSD, #OpenBSD, #DragonflyBSD, #MidnightBSD but also of some other niche systems like #illumos

Unfortunately, this might still take some time and fully relies on the spare time of @gyptazy.

#freeVPS #VPS #BSD #Box #BoxyBSD #gyptazy #opensource #education #community #foss #runbsd #hosting #freehosting #learning #ipv6

@jan Which vps provider, so we can steer clear of them? #ipv6

There you go. IPv6 Reverse DNS. Why not ?

Pronto. See you guys. Next episode, later tonight. Maybe. No promises.

#freeBSD #IPv6 #dns #reversedns

Alt...

#freeBSD #IPv6 #dns #reversedns

https://blog.apnic.net/2025/08/25/the-ipv6-divide/

#ipv6 #blog #apnic
#notbyGeoffHuston

In general, I like netcup. The FediMeteo VPS rocks and they're quite reliable but....their IPv6 implementation is such a mess! Hetzner allows you to route, so each vnet jail can have its own IPv6 address. On netcup, I have never been able to achieve such a result.

#ipv6 #Networking

@nico
They don't even have an #IPv6 prefix allocated to their AS?
What a shame!

$ host -t AAAA isitfridayyet.net
isitfridayyet.net has no AAAA record

#ipv6

Predict when GitHub will deploy IPv6.

https://www.metaculus.com/questions/37128/when-will-github-deploy-ipv6/

Current community prediction is Sep 2030.

#IPv6 #github

#ipv6 #dns

https://www.theregister.com/2025/08/20/ietf_dnsop_3901bis_ipv4_ipv6/

https://datatracker.ietf.org/doc/draft-ietf-dnsop-3901bis/04/

by @tfiebig