Rubygems access via IPV6

Sean's Avatar

Sean

05 Mar, 2019 04:42 PM

Hello,

I am posting in followup to this thread closed in July 2018 regarding access to install/update rubygems over IPV6:

https://help.rubygems.org/discussions/problems/31074-timeout-error

Is there a place to monitor progress on this? I had not encountered this until my desk was moved to another location where the local dns resolvers are configured (properly) to prefer IPV6 lookups. I have had to reconfigure my workstation so that glibc's getaddrinfo() prefers IPV4 lookups first in order to install/update gems.

It would seem that Rubygems.org is publishing AAAA dns records but the webserver is not answering on this address:
$ ping6 api.rubygems.org
PING api.rubygems.org(2a04:4e42::70 (2a04:4e42::70)) 56 data bytes
^C
--- api.rubygems.org ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999ms

Versus using IPV4:
$ ping api.rubygems.org
PING rubygems.org (151.101.64.70) 56(84) bytes of data.
64 bytes from 151.101.64.70 (151.101.64.70): icmp_seq=1 ttl=54 time=25.2 ms
64 bytes from 151.101.64.70 (151.101.64.70): icmp_seq=2 ttl=54 time=25.2 ms
^C
--- rubygems.org ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 25.259/25.273/25.287/0.014 ms

Can I suggest that the issue be fixed in one of two ways -
1. stop publishing AAAA dns records
2. configure the rubygems.org servers to answer to IPV6

If there is a better place to track this issue, please post a link that I can check up on every so often. Thank you kindly!

  1. 1 Posted by Domon on 13 May, 2019 05:45 AM

    Domon's Avatar

    I'm experience the same issue.

    I really hope rubygems.org could either support IPv6 or remove the IPv6 DNS record.

    Thanks!

    Update: I restarted my computer and it works now. 

    > ping6 rubygems.org
    PING6(56=40+8+8 bytes) [...] --> 2a04:4e42::70
    16 bytes from 2a04:4e42::70, icmp_seq=0 hlim=55 time=47.723 ms
    16 bytes from 2a04:4e42::70, icmp_seq=1 hlim=55 time=43.885 ms
    16 bytes from 2a04:4e42::70, icmp_seq=2 hlim=55 time=43.465 ms
    16 bytes from 2a04:4e42::70, icmp_seq=3 hlim=55 time=42.693 ms
    16 bytes from 2a04:4e42::70, icmp_seq=4 hlim=55 time=46.918 ms
    
  2. Support Staff 2 Posted by sonalkr132 on 13 Jul, 2020 07:47 AM

    sonalkr132's Avatar

    Hi,

    Sorry about the delay in response here. Can you please confirm if this is still an issue? If yes, I would like to forward some debugging info about your host/IP to the Fastly team.

    Thank you for your patience.

  3. 3 Posted by Braxton on 25 Aug, 2020 02:26 AM

    Braxton's Avatar

    Signing up just to comment. Yes @sonalkr132, this is still an issue.

  4. Support Staff 4 Posted by sonalkr132 on 25 Aug, 2020 06:12 AM

    sonalkr132's Avatar

    Hi Braxton,

    Thank you for reaching out. It would be very helpful if you can take some to run some commands for debugging info. Specifically, what is the output of the following commands when running from the host which has IPv6 connection issue to rubygems.org:

    $ wget -6 rubygems.org
    $ wget -6 www.ttora.com
    $ traceroute 2a04:4e42::70
    
    If you are feeling particularly generous, please add send pcap file for requests to rubygems.org over IPv6 as well. You can use tshark -i any -f "host rubygems.org" -w rubygems.pcap or sudo tcpdump -i any host rubygems.org -w rubygems.pcap

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac