The DNS record for wildcard.fedoraproject.org includes an AAAA record for 2600:1f14:fad:5c02:3556:f9be:1874:bdc0, but I cannot reach this address from my home and from three cloud providers. This causes delays when I use koji, bodhi, or fedpkg commands on my local workstation.
2600:1f14:fad:5c02:3556:f9be:1874:bdc0
koji
bodhi
fedpkg
$ mtr -n -c 10 -w 2600:1f14:fad:5c02:3556:f9be:1874:bdc0 Start: 2022-06-28T14:21:23+0000 HOST: dfw-icanhaz.mhtx.net Loss% Snt Last Avg Best Wrst StDev 1.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 2.|-- 2001:19f0:fc01:a::6464:6401 0.0% 10 0.7 0.7 0.5 0.8 0.1 3.|-- 2001:19f0:fc00::a4e:99 0.0% 10 1.4 1.5 0.9 4.4 1.0 4.|-- 2001:19f0:fc00::a4e:f9 0.0% 10 1.1 3.6 1.1 15.2 5.0 5.|-- 2001:668:0:3:ffff:2:0:d9 0.0% 10 0.4 4.9 0.4 36.7 11.3 6.|-- 2001:668:0:2:ffff:0:5995:b726 0.0% 10 27.4 33.0 27.1 82.2 17.3 7.|-- 2001:668:0:3:ffff:2:0:156a 0.0% 10 27.2 27.3 27.1 27.6 0.2 8.|-- 2620:107:4000:8000::40 0.0% 10 36.9 36.7 36.4 37.0 0.2 9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
As soon as possible would be great!
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble, ops
I might have fixed this, but I am not fully sure, can you test?
It now works from most places, but it fails from my home connection (using a tunnelbroker.net ipv6 tunnel).
So I still cannot reach 2600:1f14:fad:5c02:3556:f9be:1874:bdc0, but I don't see it in the AAAA responses for wildcard.fedoraproject.org, so this looks good! Is that what you expected?
It looks like the unreachable system is in DNS again but it's unreachable still (along with another unreachable IPv6 address):
❯ dig AAAA +short wildcard.fedoraproject.org | xargs fping major@equinix 2620:52:3:1:dead:beef:cafe:fed7 is alive 2604:1580:fe00:0:dead:beef:cafe:fed1 is alive 2600:2701:4000:5211:dead:beef:fe:fed3 is alive 2620:52:3:1:dead:beef:cafe:fed6 is alive 2600:1f14:fad:5c02:3556:f9be:1874:bdc0 is unreachable 2605:bc80:3010:600:dead:beef:cafe:fed9 is unreachable
OSUOSL ipv6 is broken currently after a network change. It looks like these were added when the ipv4 came back.
I have removed the servers and added some others.
Metadata Update from @smooge: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.