4 ms·

Get notified when GitHub IPv6 support is Live

38 points by tonymet 3y ago

miyuru 3y ago
Is it possible to change the dig server to fd00:ec2::253 from the IPv4 one. https://isgithubipv6.live/detail.txt https://isgithubipv6.live/detail.txt
- 0xFEE1DEAD 3y ago
  fd00:ec2::253 is a local address. also querying a ipv6 dns doesn't give me a result
  - ale42 3y ago
    The 169.254.169.254 DNS mentioned on the details page is also a local address. It's probably their internal DNS, so an fd00:: could also work, supposing they have one...
  - miyuru 3y ago
    169.254.169.254 is the AWS VPC DNS address. It might be used on some others providers as well but creator had some blog posts with AWS[1], so I assumed the he uses it. fd00:ec2::253 is the similar one IPv6 on AWS. [1]https://tonym.us/category/aws.html https://tonym.us/category/aws.html
    - tonymet 3y ago
      good eye. this app is running on GCP Cloud run, and they use a similar design. I'll look into the fix.
      - miyuru 3y ago
        thanks
- tonymet 3y ago
  good attention to detail. i'll look into it
- tonymet 3y ago
  oddly the docker host was not configuring ipv6 DNS server so i updated to call google dns directly SERVER: 2001:4860:4860::8888#53(2001:4860:4860::8888) (UDP)
yoelo 3y ago
Is there some kind of list out there on IPv6 support of popular APIs? Would love to eliminate IPv4 egress but not even Stripe supports IPv6 for their API yet
- orangeboats 3y ago
  Technically there is https://gosix.net https://gosix.net for this kind of stuff, but the database is very incomplete. I believe the website was created merely months ago.
  - remram 3y ago
    GitHub's entry there: https://gosix.net/en/database/websites/git/githubcom https://gosix.net/en/database/websites/git/githubcom
    - p1mrx 3y ago
      > The domain doesn't even have an AAAA record to begin with. The is the worst ranking a webite can get in the IPv6 database. You are *tearing* me *apart* GitHub!
remram 3y ago
This is only necessary because GitHub uses discussions to track requests instead of issues. I don't know why people insist on doing that. Issues have a very handy feature allowing you to be notified of specific events, like when it gets closed, but for discussions you can only subscribe to every new comment.
- tonymet 3y ago
  The app is checking AAAA records directly so we'll get notified within real-time when the changes are deployed.
rany_ 3y ago
For context, they had a service disruption a week ago due to preparations for IPv6 support on GitHub.com: https://www.githubstatus.com/incidents/5y8b8lsqbbyq https://www.githubstatus.com/incidents/5y8b8lsqbbyq. I don't think they mentioned this anywhere else. Copied from that report: This incident was the result of an infrastructure change that was made to our load balancers to prepare us for IPv6 enablement of GitHub.com. This change was deployed to a subset of our global edge sites. The change had the unintended consequence of causing IPv4 addresses to start being passed as an IPv4-mapped IPv6-compatible address to our IP Allow List functionality. For example 10.1.2.3 became ::ffff:10.1.2.3. While our IP Allow List functionality was developed with IPv6 in mind, it wasn't developed to handle these mapped addresses, and hence started blocking requests as it deemed these to be not in the defined list of allowed addresses. Request error rates peaked at 0.23% of all requests.

38 points by tonymet 3y ago

Is it possible to change the dig server to fd00:ec2::253 from the IPv4 one. https://isgithubipv6.live/detail.txt https://isgithubipv6.live/detail.txt

0xFEE1DEAD 3y ago
fd00:ec2::253 is a local address. also querying a ipv6 dns doesn't give me a result
- ale42 3y ago
  The 169.254.169.254 DNS mentioned on the details page is also a local address. It's probably their internal DNS, so an fd00:: could also work, supposing they have one...
- miyuru 3y ago
  169.254.169.254 is the AWS VPC DNS address. It might be used on some others providers as well but creator had some blog posts with AWS[1], so I assumed the he uses it. fd00:ec2::253 is the similar one IPv6 on AWS. [1]https://tonym.us/category/aws.html https://tonym.us/category/aws.html
  - tonymet 3y ago
    good eye. this app is running on GCP Cloud run, and they use a similar design. I'll look into the fix.
    - miyuru 3y ago
      thanks
tonymet 3y ago
good attention to detail. i'll look into it
tonymet 3y ago
oddly the docker host was not configuring ipv6 DNS server so i updated to call google dns directly SERVER: 2001:4860:4860::8888#53(2001:4860:4860::8888) (UDP)

yoelo 3y ago

Is there some kind of list out there on IPv6 support of popular APIs? Would love to eliminate IPv4 egress but not even Stripe supports IPv6 for their API yet

orangeboats 3y ago
Technically there is https://gosix.net https://gosix.net for this kind of stuff, but the database is very incomplete. I believe the website was created merely months ago.
- remram 3y ago
  GitHub's entry there: https://gosix.net/en/database/websites/git/githubcom https://gosix.net/en/database/websites/git/githubcom
  - p1mrx 3y ago
    > The domain doesn't even have an AAAA record to begin with. The is the worst ranking a webite can get in the IPv6 database. You are *tearing* me *apart* GitHub!

remram 3y ago

This is only necessary because GitHub uses discussions to track requests instead of issues. I don't know why people insist on doing that. Issues have a very handy feature allowing you to be notified of specific events, like when it gets closed, but for discussions you can only subscribe to every new comment.

tonymet 3y ago
The app is checking AAAA records directly so we'll get notified within real-time when the changes are deployed.

rany_ 3y ago

For context, they had a service disruption a week ago due to preparations for IPv6 support on GitHub.com: https://www.githubstatus.com/incidents/5y8b8lsqbbyq https://www.githubstatus.com/incidents/5y8b8lsqbbyq. I don't think they mentioned this anywhere else. Copied from that report: This incident was the result of an infrastructure change that was made to our load balancers to prepare us for IPv6 enablement of GitHub.com. This change was deployed to a subset of our global edge sites. The change had the unintended consequence of causing IPv4 addresses to start being passed as an IPv4-mapped IPv6-compatible address to our IP Allow List functionality. For example 10.1.2.3 became ::ffff:10.1.2.3. While our IP Allow List functionality was developed with IPv6 in mind, it wasn't developed to handle these mapped addresses, and hence started blocking requests as it deemed these to be not in the defined list of allowed addresses. Request error rates peaked at 0.23% of all requests.