On 30.06.2015 17:07, Matthew Miller wrote: > With the DNSSEC feature enabled as per the testing instructions, I'm > sometimes (but not always) getting failures for popular geek blog Boing > Boing, when public DNS still works: > > $ host boingboing.net > Host boingboing.net not found: 2(SERVFAIL) > > $ host boingboing.net 8.8.8.8 > Using domain server: > Name: 8.8.8.8 > Address: 8.8.8.8#53 > Aliases: > > boingboing.net is an alias for boingboing.net.global.prod.fastly.net. > boingboing.net.global.prod.fastly.net is an alias for > global-ssl.fastly.net. > global-ssl.fastly.net is an alias for fallback.global-ssl.fastly.net. > fallback.global-ssl.fastly.net has address 199.27.76.249 > fallback.global-ssl.fastly.net has address 23.235.46.249 > > What's going on here? How can I diagnose it, and how can we fix it so > that users don't have to diagnose these situations? > > I'm concerned that if it's happening with this site (which Alexa rates > as in the top 1000 websites in the US), it'll happen with a lot of > others. > Hi Matt. Please file a bug against dnssec-trigger. It will be better for getting additional information. Also please see the reply by Paul Wouters to your previous email. Thanks in advance. Regards, -- Tomas Hozza Software Engineer - EMEA ENG Developer Experience PGP: 1D9F3C2D Red Hat Inc. http://cz.redhat.com -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
