▲ 6 ▼ Yearly reminder that github still does not have an IPv6 address (2023) (sopuli.xyz) submitted 3 years ago by Sibbo@sopuli.xyz to c/programming@programming.dev 16 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.
[–] Wats0ns@programming.dev 0 points 3 years ago (1 child) But why ? permalink fedilink source parent hideshow 2 child comments replies: [–] astral_avocado@programming.dev -1 points 3 years ago I am not a full network engineer so take my opinion with a grain of salt. From what I understand, NAT with IPv4 works really really well to mitigate IPv4 address exhaustion. Then there's an issue with the amount of extra processing switches and routers need to do IPv6, we're going from 32 bits to 128 bits which is a huge increase and for switches and routers that are handling packets as fast as technically possible with a low amount of resources typically, that's a not insignificant hurdle. It's just easier to do IPv4 in every way, plus that's what the world's been using and is used to. permalink fedilink source parent
[–] astral_avocado@programming.dev -1 points 3 years ago I am not a full network engineer so take my opinion with a grain of salt. From what I understand, NAT with IPv4 works really really well to mitigate IPv4 address exhaustion. Then there's an issue with the amount of extra processing switches and routers need to do IPv6, we're going from 32 bits to 128 bits which is a huge increase and for switches and routers that are handling packets as fast as technically possible with a low amount of resources typically, that's a not insignificant hurdle. It's just easier to do IPv4 in every way, plus that's what the world's been using and is used to. permalink fedilink source parent