Seems more widespread and affecting the backend of Dyn. The fact that I get SERVFAIL sometimes means their DNS answered - Just couldn't give me THE answer :)
I've tested it from Ashburn, VA, Miami, FL, New York, NY and Chicao, IL. Chicago is the only one that worked. On Fri, Oct 21, 2016 at 9:13 AM, Patrick W. Gilmore via Outages <outages@outages.org> wrote: > Attack just re-started. > > Watch your flows. Help out if you can. > > -- > TTFN, > patrick > > On Oct 21, 2016, at 12:12 PM, Terry Hardie via Outages <outages@outages.org> > wrote: > > Even though their page says the outage is resolved, I'm still getting > DNS failures (return SERVFAIL, not no answer) to their anycast > networks from California: > > $ dig @ns2.p34.dynect.net video.twimg.com > > ; <<>> DiG 9.3.2 <<>> @ns2.p34.dynect.net video.twimg.com > ; (1 server found) > ;; global options: printcmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 170 > ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 > > ;; QUESTION SECTION: > ;video.twimg.com. IN A > > ;; Query time: 3103 msec > ;; SERVER: 204.13.250.34#53(204.13.250.34) > ;; WHEN: Fri Oct 21 17:11:36 2016 > ;; MSG SIZE rcvd: 33 > _______________________________________________ > Outages mailing list > Outages@outages.org > https://puck.nether.net/mailman/listinfo/outages > > > > _______________________________________________ > Outages mailing list > Outages@outages.org > https://puck.nether.net/mailman/listinfo/outages > _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
