[Outages-discussion] Dyn outage continuing

[Seth Mattinen]

On 10/21/16 10:16, Chris Adams wrote:
> [moved to outages-discussion]
>
> Once upon a time, Patrick W. Gilmore via Outages <outages at outages.org> said:
>> > 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.
> The flip side is that the concentration of services in "specialist"
> hands makes it easier to attack a large number of companies at once.  If
> PagerDuty ran their own DNS, they are not a likely target of an attack,
> so would be unaffected.


PagerDuty should, at minimum, run their own DNS in addition to using 
someone like Dyn. Not put all their DNS eggs in a single basket.

Maybe Dyn needs to deploy anycast nodes at every internet exchange of 
every size and scale instead of relying on a small number of beefy 
anycast nodes in select locations if their customers are going to have a 
single point of failure.

Look at eBay:

ebay.com.		172800	IN	NS	sjc-dns1.ebaydns.com.
ebay.com.		172800	IN	NS	sjc-dns2.ebaydns.com.
ebay.com.		172800	IN	NS	smf-dns1.ebaydns.com.
ebay.com.		172800	IN	NS	smf-dns2.ebaydns.com.
ebay.com.		172800	IN	NS	ns1.p47.dynect.net.
ebay.com.		172800	IN	NS	ns2.p47.dynect.net.
ebay.com.		172800	IN	NS	ns3.p47.dynect.net.
ebay.com.		172800	IN	NS	ns4.p47.dynect.net.

But then PayPal falls flat:

paypal.com.		172800	IN	NS	ns1.p57.dynect.net.
paypal.com.		172800	IN	NS	ns2.p57.dynect.net.
paypal.com.		172800	IN	NS	ns3.p57.dynect.net.
paypal.com.		172800	IN	NS	ns4.p57.dynect.net.

~Seth