DDoS attacks against Zerigo DNS services

Implementing secondary DNS servers is essential, and has kept our primary site up and running.<p>That said, it is UNFORGIVABLE (imo) that Zerigo failed to send ANY type of notification to its DNS customers... they have apparently been having ddos trouble for about 24 hours.<p>afaik they do not offer any type of text or email alerts when they are experiencing trouble (such as the SMS messages I get from Heroku).<p>So, while I like their tools, and the ddos hasn&#x27;t affected our website that have secondary DNS, we will &quot;walk&quot; to another provider that cares enough about their customers to offer proactive alerts.

Honestly I&#x27;ve tried most of the popular DNS providers (DNSMadeSimple, DynDNS, etc), but nothing lets me and my team sleep tighter at night than Route53. If a DDos is successful in taking down Amazon Route53, then we have bigger issues to worry about. Plus, Route53 is dirt cheap, its a no brainer.

Just a heads up, Zerigo doesn&#x27;t operate its own network for DNS, so as far as mitigating an attack they are at the mercy of upstreams.<p>a.ns.zerigo.net 64.27.57.11, announced by WeHostWebSites.com<p>b.ns.zerigo.net 174.37.229.229, SoftLayer<p>c.ns.zerigo.net 109.74.192.232, Linode<p>d.ns.zerigo.net 174.36.24.250, Softlayer<p>e.ns.zerigo.net 72.26.219.150, Voxel.net (Internap)<p>f.ns.zerigo.net 223.27.170.242, Voxel.net (Internap)

First DNSimple and now Zerigo. I wonder if this is coordinated or if it&#x27;s separate groups. In any case I&#x27;m glad I switched to Route53 a few weeks ago.

Are these attacks part of a strategy to take down a specific target(s) or are they basically shotgunning providers?