Hi all,
I got this when trying to clone a repo from github and an IPv6 only host:
[minfrin@bob openwrt]$ git clone https://github.com/openwrt/packages.git
Cloning into 'packages'...
fatal: unable to access 'https://github.com/openwrt/packages.git/': Couldn't connect to server
caused by this:
[minfrin@bob openwrt]$ host -t AAAA github.com
github.com has no AAAA record
When will github make itself available on the IPv6 internet?
Regards,
Graham
–
Since github is now owned by Microsoft, they are probably using azure to host it. Most of azure stuff (app services eg.) aren’t available on ipv6. Maybe this call should be bigger, something like
@microsoft-365 can you make your services available on the new ipv6 network
Microsoft have supported IPv6 on a lot of things for a long time, e.g. Office 365 is fully IPv6 capable.
While things like App Services don’t support IPv6, there are easy and commonly deployed methods to IPv6-enable them, including one as part of Azure: Front Door…
IPv6 is also not “new”, it has been around for over 20 years…
If you’re looking for a workaround: Use a proxy that has IPv4 connectivity. What kind of proxy would depend on your needs, to just clone/pull a HTTP proxy would be sufficient.
And I agree that IPv6 is not optional for any service (and hasn’t been for a while, really).
any update on this? also doesn’t GitHub has a network engineering team to work on IPv6.
you are breaking the web by not supporting IPv6.
Its look like. This is a secondary issue to them. They might do it in future. They don’t have a roadmap on this. As i rem.
this is crazy! It was the last site I expected to have no IPv6 support.
Can someone explain why github does not support IPv6?
@bobhinden Its hard to setup ipv6. Because infrastructure is complex and doesn’t support ipv4. The hardware is exclusive for ipv6 and ipv4 separately. Its not a christmas cake which u can bake in 2 hours. There are complex things like routing. Also more people use github pages. That means everything need to change. Too much stuff to work.
I’m sorry, but that’s wrong. Anything that supports Ethernet (there are other options, but Ethernet is super common) can do IPv6 as long as the software supports it, and all modern operating systems do. Routing isn’t any more complex than for IPv4, one thing that might add some complexity is prefix delegation (for dynamically distributing routeable subnets, instead of using private networks and NAT).
I don’t know either why GitHub still doesn’t support IPv6. My guess is that it’s either not a priority (someone would need to do the work), or they rely on hosting that doesn’t support IPv6 and moving is considered too much trouble for now.
Means you want to say. i’m not completely correct. comon read again. I mean the same. you are saying hosting doesn’t support and im saying infrasture. The hosting provider of github may not provide the same because you have to replace every machine and upgrade which support ipv6. That’s what i’m saying…
to be very clear- The device which support only ipv4 doesn’t support ipv6. and ipv6 doesn’t support ipv4. Its not USB - like if u have usb 3.0 then it will work on usb 2.0. That’s backward capability. Backward capability is not supported in IPV6 … Make your facts correct.
You can’t open a ipv6 only website with ipv4 ISP There is no backward capability. That’s only reason why everything is not on ipv6
SO you need lots of money and time and infrastructure to setup new machine.
You always make my statement nulll. Try to be clear and exact what’s wrong. Not just You are wrong. I don’t want to rant on you on github community post.
Yes, a device that is configured to use only one of the protocols won’t be able to reach one that uses only the other. But it is no problem to configure IPv4 and IPv6 on the same device, on the same link. That’s usually called dual-stack, it exists specifically for backwards compatibility, and has been the default on most operating systems for years. 
If a connectivity or hosting provider refuses to provide IPv6 then yes, it is probably the only option to take business elsewhere, and that may be a bunch of trouble. But that has nothing to do with IPv6 itself, it’d be the same with any other problems regarding that provider’s service.
This is your weekend project - go to https://tunnelbroker.net, and get a free IPv6 tunnel and set it up. Complete their IPv6 certification program.
For anyone still interested, Google Source Repositories can sync your GitHub repos and is accessible over ipv6:
Gentle suggestion that when Bob Hinden asks why Github doesn’t support IPv6, the answer he’s looking for is probably more detailed than a brief explainer about what is IPv6 and that it’s not a cake. He probably knows that.
https://datatracker.ietf.org/person/Bob%20Hinden
The cynical answer to Bob’s question is probably: if you can only get to Github over IPv4, then that means you need to pay by the minute to spin up a Managed NAT Gateway so your IPv6-only hosts can access Github because see that’s the problem with supporting IPv6— all the damned free riders who aren’t willing to pay for IPv4 addresses and managed NAT gateways.
The rent must be paid, don’t you know.
Something is happening 
Maybe this alternative can meet your needs:
1: fork project
2: Import the github project on your gitlab
3: clone with https on your gitlab(because gitlab supports ipv6)
IPv4 is at the end of life. Some servers are getting up and running only with IPv6. When Microsoft would enable this protocol ? It is not a feature anymore, it is needed.