= bug description = IPv6 address 2610:28:3090:3001:5054:ff:feb9:6ae0 (fedorapeople.org) not reachable from external.
= bug analysis = {{{ $ w3m http://[2610:28:3090:3001:5054:ff:feb9:6ae0] w3m: Can't load http://[2610:28:3090:3001:5054:ff:feb9:6ae0]. $ }}}
= fix recommendation = Given that eth0 on people01.fedoraproject.org has the IPv6 address 2610:28:3090:3001:5054:ff:feff:683f/64 configured/assigned, the DNS should be simply updated accordingly.
From my point of view, the fix is:
{{{ --- a/master/fedorapeople.org +++ b/master/fedorapeople.org @@ -1,7 +1,7 @@ ; -- mode: zone -- $TTL 3600 @ IN SOA ns04.fedoraproject.org. hostmaster.fedorapeople.org. ( - 2015070801 ; Serial + 2015071201 ; Serial 1H ; refresh 1M ; retry 4W ; expire @@ -13,9 +13,9 @@ $TTL 3600 @ IN NS ns05.fedoraproject.org.
@ IN A 152.19.134.196 -@ IN AAAA 2610:28:3090:3001:5054:ff:feb9:6ae0 +@ IN AAAA 2610:28:3090:3001:5054:ff:feff:683f * IN A 152.19.134.196 - IN AAAA 2610:28:3090:3001:5054:ff:feb9:6ae0 + IN AAAA 2610:28:3090:3001:5054:ff:feff:683f
; ssh keys fedorapeople.org. IN SSHFP 1 1 5829b0460c2e9296bdbd835416c2615dcf80d22a }}}
Unfortunately I am not a member of the sysadmin-dns group, so I can not run ./do-domains to update the DNSSEC related records. So can somebody else please apply the fix?
This has been fixed in the DNS repo (I also fixed fedora planet.org, which is the same host.
This will go live when someone next runs the update_dns playbook (unfortunately I don't have my token with me right now). Will run it tomorrow morning.
Login to comment on this ticket.