GitHub seems to be enabling IPv6 for GitHub Pages
21–30 of 57 posts
Re: GitHub seems to be enabling IPv6 for GitHub Pages
#22> GitHub seems to be enabling IPv6 for GitHub Pages This is extremely misleading at best. As far as I can tell from reading this stuff, the only thing that has changed recently is that github-repository-files.githubusercontent.com has started serving an AAAA record. (Perhaps other subdomains as well, but that’s the only one reported and it’s definitely not all.) That’s nothing to do with GitHub Pages. GitHub Pages ha…
> AAAA record
Tangent here. Does anyone know why DNS record names are so terrible? Why are there records named after batteries?
Re: GitHub seems to be enabling IPv6 for GitHub Pages
#23It would be nice if Verizon was interested in providing IPv6 access via their Fios service at all in 2021.
It would be nice to see this forced by law.
It should be as simple as not being allowed to advertise a service as providing Internet unless it provides 100% native, full-featured IPv6.
Imagine if in 2001 some company tried to sell an "Internet service" that didn't provide IPv4, or only provided RFC1918 addresses, or didn't allow something as trivial as non-NAT routing of IPv4, even as an option. They'd be sued for false advertising, and rightly so.
Meanwhile, in 2021 tier-1 cloud providers like Azure have an absolute shitshow of partial IPv6 support, yet they get away with advertising that they provide "Internet connectivity". They provide only private ranges, and force NAT for all IPv6 traffic. The vast majority of their services are IPv4 only, so enabling IPv6 is mostly pointless. Worse, if you do enable IPv6 on their virtual networks, this then disables unrelated IPv4 functionality. It's madness.
Re: GitHub seems to be enabling IPv6 for GitHub Pages
#24Re: GitHub seems to be enabling IPv6 for GitHub Pages
#25Earlier quoted context omitted.
It would be nice to see this forced by law.
It should be as simple as not being allowed to advertise a service as providing Internet unless it provides 100% native, full-featured IPv6. Imagine if in 2001 some company tried to sell an "Internet service" that didn't provide IPv4, or only provided RFC1918 addresses, or didn't allow something as trivial as non-NAT routing of IPv4, even as an option . They'd be sued for false advertising, and rightly so. Meanwhile,…
I run a full dual stack service in Azure [1]. I couldn’t get instance level IPv6 working, but everything else works in both v4 and v6.
I will echo that many Azure services don’t support v6 yet, though.
https://docs.microsoft.com/en-us/azure/virtual-network/ipv6-...
Re: GitHub seems to be enabling IPv6 for GitHub Pages
#26> GitHub seems to be enabling IPv6 for GitHub Pages This is extremely misleading at best. As far as I can tell from reading this stuff, the only thing that has changed recently is that github-repository-files.githubusercontent.com has started serving an AAAA record. (Perhaps other subdomains as well, but that’s the only one reported and it’s definitely not all.) That’s nothing to do with GitHub Pages. GitHub Pages ha…
> AAAA record Tangent here. Does anyone know why DNS record names are so terrible? Why are there records named after batteries?
A means address. The IPv6 variant is called AAAA because IPv6 addresses are 4x longer than IPv4 addresses.
Re: GitHub seems to be enabling IPv6 for GitHub Pages
#27I'm surprised they didn't have it until now. Every cloud provider's load balancer and CDN has had IPv6 for a while. That they don't have it for the site or SSH is less surprising, but GitHub Pages is static content.
Maybe AWS, Azure, and GCP, but not places like Digital Ocean. IPv6 is still very niche, and it's suffering from that effect where it being very niche keeps it very niche. Nobody wants to be an early adopter (and momentum seems to be dying), and the result is that there's no adoption.
I think we've been trying to make IPv6 happen since 1998, and ... it's not happening.
Re: GitHub seems to be enabling IPv6 for GitHub Pages
#28> GitHub seems to be enabling IPv6 for GitHub Pages This is extremely misleading at best. As far as I can tell from reading this stuff, the only thing that has changed recently is that github-repository-files.githubusercontent.com has started serving an AAAA record. (Perhaps other subdomains as well, but that’s the only one reported and it’s definitely not all.) That’s nothing to do with GitHub Pages. GitHub Pages ha…
> AAAA record Tangent here. Does anyone know why DNS record names are so terrible? Why are there records named after batteries?
[deleted]
Re: GitHub seems to be enabling IPv6 for GitHub Pages
#29> GitHub seems to be enabling IPv6 for GitHub Pages This is extremely misleading at best. As far as I can tell from reading this stuff, the only thing that has changed recently is that github-repository-files.githubusercontent.com has started serving an AAAA record. (Perhaps other subdomains as well, but that’s the only one reported and it’s definitely not all.) That’s nothing to do with GitHub Pages. GitHub Pages ha…
> AAAA record Tangent here. Does anyone know why DNS record names are so terrible? Why are there records named after batteries?
Probably because they wanted to keep them short. AAAA records are so named because it is the ipv6 equivalent of an A record, and ipv6 addresses are four times as long as ipv4 addresses. I agree it is pretty terrible though.
Re: GitHub seems to be enabling IPv6 for GitHub Pages
#30Earlier quoted context omitted.
> AAAA record Tangent here. Does anyone know why DNS record names are so terrible? Why are there records named after batteries?
A means address. The IPv6 variant is called AAAA because IPv6 addresses are 4x longer than IPv4 addresses.
Also, A6 is probably a better name, but it has a worse (unworkable?) format, so AAAA is a reasonable second choice.