this post was submitted on 25 Jul 2023
255 points (98.1% liked)

Programming

17541 readers
79 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago
MODERATORS
snowe
Ategon
[email protected]
255
Yearly reminder that github still does not have an IPv6 address (2023) (sopuli.xyz)
submitted 1 year ago by [email protected] to c/programming
54 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 12 points 1 year ago

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.