This is just a horribly painful example of why we/they should all follow the route of NetFlix ( http://techblog.netflix.com/2013/05/denominating-multi-region-sites.html ) and use multiple DNS providers. Denominator ( https://github.com/Netflix/denominator ) the tool NetFlix uses for this and open-sourced, currently supports managing (mirrored) DNS records across AWS Route53, RackSpace CloudDNS, DynECT and UltraDNS.
-Jason On Fri, Oct 21, 2016 at 1:09 PM, Patrick W. Gilmore via Outages < outages@outages.org> wrote: > It is a shame in that PagerDuty is affected. > > However, Dyn is far, far better positioned to withstand attacks than a > company like PagerDuty could possibly be on their own. So I think PagerDuty > did the right thing in using Dyn. > > Remember, Twitter, Pingdom, github, and lots of other people use Dyn. And > this is the first major outage I have heard of their service. > > Let’s all be clear that Dyn has to be in the top 10 DNS infrastructures on > the planet. Possibly the largest that sells DNS as a service. This is a > serious attack, and the entire community should help track this miscreant > down, then crush them like a bug. > > -- > TTFN, > patrick > > On Oct 21, 2016, at 1:00 PM, Terry Hardie via Outages <outages@outages.org> > wrote: > > It's a shame services like PagerDuty use Dyn. Now they're down too... > > On Fri, Oct 21, 2016 at 9:57 AM, Justin Krejci via Outages > <outages@outages.org> wrote: > > Previously it was not affecting upper midwest for me, traces went to > Chicago. > > Now traces to twitter DNS servers in Chicago are failing. > > > ________________________________ > From: Neil Hanlon via Outages [outages@outages.org] > Sent: Friday, October 21, 2016 11:16 AM > To: Terry Hardie; outages@outages.org > Subject: Re: [outages] Dyn outage continuing > > The attacks appear to be continuing again. We are experiencing issues in > Europe/Asia. > > On Fri, Oct 21, 2016 at 12:13 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 > > > -- > > KAYAK > > Neil Hanlon > > Devops Engineer > > > +1 978 902 8171 > > _______________________________________________ > 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 > >
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
