[Outages-discussion] [outages] Dyn outage continuing

[Kevin Blackham]

FWIW, AWS made some changes... today, I think? They're now very diversified.

us-east-1.amazonaws.com. 600   IN     NS     ns4.p31.dynect.net.
us-east-1.amazonaws.com. 600   IN     NS     u1.amazonaws.com.
us-east-1.amazonaws.com. 600   IN     NS     u3.amazonaws.com.
us-east-1.amazonaws.com. 600   IN     NS     u4.amazonaws.com.
us-east-1.amazonaws.com. 600   IN     NS     pdns1.ultradns.net.
us-east-1.amazonaws.com. 600   IN     NS     u2.amazonaws.com.
us-east-1.amazonaws.com. 600   IN     NS     pdns5.ultradns.info.
us-east-1.amazonaws.com. 600   IN     NS     u6.amazonaws.com.
us-east-1.amazonaws.com. 600   IN     NS     pdns3.ultradns.org.
us-east-1.amazonaws.com. 600   IN     NS     u5.amazonaws.com.
us-east-1.amazonaws.com. 600   IN     NS     ns1.p31.dynect.net.
us-east-1.amazonaws.com. 600   IN     NS     ns3.p31.dynect.net.
us-east-1.amazonaws.com. 600   IN     NS     ns2.p31.dynect.net.

Now if the rest of the admins out there will figure out that if their
service is depended on by more than 100 companies, they should really think
about spreading their dns around. I'm very afraid of what happens when
route53 gets knocked out.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages-discussion/attachments/20161021/8d6716e9/attachment.html>