[HN Gopher] GitHub seems to be enabling IPv6 for GitHub Pages
       ___________________________________________________________________
        
       GitHub seems to be enabling IPv6 for GitHub Pages
        
       Author : scrollaway
       Score  : 89 points
       Date   : 2021-08-14 13:06 UTC (9 hours ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | dheera wrote:
       | Too bad I often have to disable IPv6 because my ISP suddenly
       | decides to stop routing it from time to time.
       | 
       | This is Comcast, so arguing with them doesn't get me anywhere,
       | all I get is "Thanks for expressing your concern." "Rest assured
       | that I will solve all your problems." from the support dude in
       | some random call/chat center.
        
         | rahimnathwani wrote:
         | I use both Comcast and Monkeybrains. I've had to disable IPv6
         | only once in the last 18 months: for my Monkeybrains
         | connection.
        
         | gtirloni wrote:
         | Same here. I had enough random problems when IPv6 was enabled
         | and got tired of troubleshooting things. Just disabled it and
         | will enable again in a few years. Hopefully things will be
         | better.
        
         | miyuru wrote:
         | Doesn't Happy Eyeballs fallback to IPv4 on that situation?
        
           | formerly_proven wrote:
           | Anecdata: Enabling IPv6 does seem to break random stuff
           | randomly.
        
             | wongarsu wrote:
             | If something has a network problem but it's not the uplink
             | and it isn't DNS, then disabling ipv6 is definitely the
             | next in the list.
        
           | dheera wrote:
           | Maybe it's supposed to in theory but empirical results on my
           | machine say it doesn't
        
       | ahmedfromtunis wrote:
       | Silly question (especially for this forum): how would ipv6 be
       | useful for websites served via Github Pages?
        
         | andrewjf wrote:
         | There are more and more networks that are native IPv6. And IPv4
         | connectivity is done with double NAT, NAT64, 464XLAT and other
         | heroics.
         | 
         | The faster we can allow native IPv6 end-to-end, the faster we
         | can get rid of the complex IPv4 compatibility technologies and
         | simplify the entire internet. At some point, you may start to
         | see networks with no v4 connectivity whatsoever (maybe they
         | already exist, but I can't imagine them being useful), so this
         | allows those users to reach github pages.
         | 
         | To directly answer your question, it's investment and
         | maintenance in infrastructure, not for user features.
        
           | rnhmjoj wrote:
           | > maybe they already exist, but I can't imagine them being
           | useful
           | 
           | They are rare but do exist! Here's a couple of reports from
           | the IPv6 subreddit: [1] [2].
           | 
           | [1]: https://teddit.net/r/ipv6/comments/he38ga/work_has_turne
           | d_of...
           | 
           | [2]: https://teddit.net/r/ipv6/comments/n5y5oo/update_on_not_
           | bein...
        
       | [deleted]
        
       | chrismorgan wrote:
       | > _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 has unofficially
       | supported IPv6 for more than three years apart from the DNS
       | records, so if you're brave or foolish enough you could add AAAA
       | records on a custom domain that's handled by GitHub Pages.
        
         | lima wrote:
         | Don't underestimate the amount of backend plumbing necessary to
         | enable this kind of thing at scale, even if it's "just" a CDN
         | feature flag (analytics pipeline, authorization, rate limiting,
         | and so much more...)
        
       | remram wrote:
       | I'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.
        
       | jlelse wrote:
       | But github.com is still missing...
       | 
       | https://jlelse.blog/thoughts/2021/08/github-ipv6
        
       | brirec wrote:
       | It would be nice if Verizon was interested in providing IPv6
       | access via their Fios service at all in 2021.
        
         | sodality2 wrote:
         | This user says they have IPV6 with FiOS:
         | https://news.ycombinator.com/item?id=27985103
         | 
         | I have FiOS as well and I'm only a few miles from them. I
         | attempted to get IPV6 from the router settings and it didn't
         | work for me.
        
       ___________________________________________________________________
       (page generated 2021-08-14 23:00 UTC)