On 04 Nov 2015 09:20:00 -0000 Toby Goodwin <toby@xxxxxxxxxxx> wrote: > As well as Fedora itself, we need to get the infrastructure IPv6 > ready. My company has developed an IPv6 health checker. Given a > domain, it tests its nameservers, webservers, and mailservers for > IPv6 readiness. > > Currently fedoraproject.org scores 4 out of 9, so there's some room > for improvement! > > https://www.mythic-beasts.com/ipv6/health-check?domain=fedoraproject.org > > It seems odd that there are AAAA records for ns0[25], but they point > to "dead:beef" addresses that are unreachable. Is this deliberate? no. When you see something like this, please report it to Fedora infrastructure so we can get it fixed. > Seems like it will just slow things down for any resolver that > happens to try the IPv6 address first. (And of course the domain is > completely unresolvable from a "pure" IPv6 client.) Right. I have fixed the 2 nameservers now. We now score 7 of 9. The other 2 points seem to be for ipv6 MX records. I'm not sure thats likely to change anytime soon. We currently have redhat.com handle our incoming emails to fedoraproject.org and do some spam filtering, etc. While we could change this, it's not something we want to do quickly or lightly. kevin
Attachment:
pgpdhWdNjT2kM.pgp
Description: OpenPGP digital signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
