While reviewing how to find which proxies were not working on ipv6 I noticed that several proxies had ipv6 addresses in wildcard but not reflected in their own DNS.
diff --git a/fedoraproject.org.template b/fedoraproject.org.template index aab3fb49..4a9cf53d 100644 --- a/fedoraproject.org.template +++ b/fedoraproject.org.template @@ -771,13 +771,16 @@ proxy32 IN A 18.192.40.85 ;proxy32 IN AAAA 2406:da12:0:c10:ce4f:44af:c7b4:3a88 proxy32 IN TXT "aws:frankfurt" proxy33 IN A 13.246.137.48 +proxy33 IN AAAA 2406:da11:911:f402:d217:23c3:1c36:be86 proxy33 IN TXT "aws:capetown" proxy34 IN A 15.228.175.157 +proxy34 IN AAAA 2600:1f1e:fa1:6501:dae3:4970:1ff0:13f2 proxy34 IN TXT "aws:saopaulo" proxy35 IN A 18.133.140.134 proxy35 IN TXT "aws:london" proxy35 IN AAAA 2a05:d01c:c6a:cc01:269:da52:9ae1:43e6 proxy36 IN A 18.159.254.57 +proxy36 IN AAAA 2a05:d014:10:7803:f774:4d7c:e277:a457 proxy36 IN TXT "aws:frankfurt" proxy37 IN A 13.233.179.58 proxy37 IN TXT "aws:mumbai"
I removed myself from sysadmin-dns a while ago due to not being active in sysadmin, but the above change should allow for fixing this
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
Metadata Update from @phsmoura: - Issue assigned to phsmoura
Thanks for finding this out @smooge I'm surprised that proxy36 didn't had it set as all the people were redirected to it when using IPv6
Yeah, that is what I was trying to replicate with a script.. and found that it is defined for wildcard.fedoraproject.org but not for itself
Note that this doesn't affect anything other than people addressing those proxys by numbers... which is... pretty much just us, or in rare cases people debugging things.
The ipv6 works fine as part of wildcard, etc.
I think @phsmoura merged this, but... proxy33 doesn't seem to actually have that address on it. ;(
yep, merged yesterday
ok. I fixed proxy33. :) Thanks everyone, lets close this.
Metadata Update from @kevin: - Issue close_status updated to: Fixed with Explanation - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.