or Create a profile
05 Mar, 2019 04:42 PM
I am posting in followup to this thread closed in July 2018 regarding access to install/update rubygems over IPV6:
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
--- 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 (18.104.22.168) 56(84) bytes of data.
64 bytes from 22.214.171.124 (126.96.36.199): icmp_seq=1 ttl=54 time=25.2 ms
64 bytes from 188.8.131.52 (184.108.40.206): icmp_seq=2 ttl=54 time=25.2 ms
--- 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!
Formatting help /
(switch to plain text)
(switch to Markdown)
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.
A conversation has been started with the RubyGems.org staff to resolve this discussion.
This discussion is private.
Only you and RubyGems.org support staff can see and reply to it.
This discussion is public. Everyone can see and reply to it.
You can use Command ⌘ instead of Control ^ on Mac
Powered by Tender™.