Just leaving this one here:
~$ dig AAAA github.com
; <<>> DiG 9.18.28-0ubuntu0.22.04.1-Ubuntu <<>> AAAA github.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33610
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
@resingm what I think is worse is that there is no ipv6 in the GitHub CI infra. GitHub host a big part of the worlds open source project but it is incredibly difficult for those to run test suites to verify that the ipv6 actually works. So it is no surprise that GitHub open source projects seldom test the ipv6 functionality.
@resingm How can ISP adopt IPv6 if the open source software they rely on does not work with IPv6? And how can the open source software verify that things work on IPv6 if they cannot test it in CI?
The low IPv6 adoption is on GitHub.
@ncopa @resingm IPv6 is older than GitHub, and older than test-driven development. While GH not having IPv6 support at all doesn’t help, IMHO the real problem is how stubborn some network operators are.
I’ve seen multiple cases where IPv6 support was treated as “experimental” - in production networks, on the public internet, just because some dude at a random IX said so. We need to get more people to demand IPv6, and if possible, switch more and more things to IPv6-first. The only way we can get better adoption is when everyone stops treating IPv6 as a second thing to do, and focuses on it first.
@weirdtreething @domi @resingm
Imagine how helpful it would be for you to be able to test it in CI, even if you cannot test it locally!