Try the following:
$ nslookup github.com
[...]
Non-authoritative answer:
Name: github.com
Address: 140.82.121.3
See also the completely ignored post in their forums.
Try the following:
$ nslookup github.com
[...]
Non-authoritative answer:
Name: github.com
Address: 140.82.121.3
See also the completely ignored post in their forums.
How hard is it to support IPv6? Does it require new hardware?
It’s not generally a hardware problem. It’s a resourcing problem. Companies like GitHub will have complex software and architecture. IPv6 requires them to get a pool of IP addresses, come up with an IP address management strategy, make sure all hosts have IPv6 addresses meaning that now provisioning systems and tooling to management DNS has to plumb IPv6 addresses through too.
Then the software stack has to support it. Maybe their fraud detection or auditing systems have to now support IPv6 which means changes to API schemas.
None of this is a good reason why they shouldn’t do it, but I’ve had to make similar decisions at my job as a software engineer on what looks to be simple but actually requires changes across systems.
I used to study networking, albeit at a pretty beginner level. IPv6 has been around for nearly 30 years at this point, so I’d be surprised if the hardware github uses doesn’t support it. The impression I got was that it’s pretty easy to extend an IPv4 address space so there isn’t any rush to make a large scale move to IPv6 everywhere.