Earlier quoted context omitted.
It's pretty wild that AWS is having impacts for the dyn outage given the shoutout to Route53. Wonder what they know that they don't?
Not sure if people are confusing Amazon with AWS in this case. $ dig +short ns amazon.com ns1.p31.dynect.net. pdns1.ultradns.net. ns4.p31.dynect.net. pdns6.ultradns.co.uk. ns3.p31.dynect.net. ns2.p31.dynect.net.
DDoS Attack Against Dyn Managed DNS
121–130 of 721 posts
Re: DDoS Attack Against Dyn Managed DNS
#122Relevant (or at least a-propos) post by Bruce Schneier, from a month ago: "Someone Is Learning How to Take Down the Internet" https://www.schneier.com/blog/archives/2016/09/someone_is_le... Edit: And to be clear: I don't mean to imply there's any connection :)
Really? It's unclear there's any connection between that vague article and Dyn's problems today.
Re: DDoS Attack Against Dyn Managed DNS
#123Relevant (or at least a-propos) post by Bruce Schneier, from a month ago: "Someone Is Learning How to Take Down the Internet" https://www.schneier.com/blog/archives/2016/09/someone_is_le... Edit: And to be clear: I don't mean to imply there's any connection :)
>We don't know who is doing this, but it feels like a large nation state. China or Russia would be my first guesses. Why not the USA?
Re: DDoS Attack Against Dyn Managed DNS
#124Re: DDoS Attack Against Dyn Managed DNS
#125Relevant (or at least a-propos) post by Bruce Schneier, from a month ago: "Someone Is Learning How to Take Down the Internet" https://www.schneier.com/blog/archives/2016/09/someone_is_le... Edit: And to be clear: I don't mean to imply there's any connection :)
>We don't know who is doing this, but it feels like a large nation state. China or Russia would be my first guesses. Why not the USA?
Re: DDoS Attack Against Dyn Managed DNS
#126Earlier quoted context omitted.
They're widely used because they were one of the few providers of geo-aware DNS service for a long time. (These days there are other, cheaper options, including Amazon Route53.)
Other option would have been Akamai's geo-aware DNS that has been available for a long time.
Re: DDoS Attack Against Dyn Managed DNS
#127I'm updating a list of confirmed outages as I see them here https://news.ycombinator.com/item?id=12759520 So far twitter, etsy, soundcloud, spotify, github, pagerduty...crazy that this can even happen
I'm surprised; I would have thought such large sites would use more than one DNS provider? I mean: $ host -t NS twitter.com twitter.com name server ns4.p34.dynect.net. twitter.com name server ns3.p34.dynect.net. twitter.com name server ns2.p34.dynect.net. twitter.com name server ns1.p34.dynect.net. I would have expected at least one of those to be somewhere else. What is the reason they would not have a backup provid…
I'm not saying it's a good reason but it's a reason.
Re: DDoS Attack Against Dyn Managed DNS
#128[deleted]
Re: DDoS Attack Against Dyn Managed DNS
#129Damn, I've spent the past 30 minutes trying to update my DNS and playing with my router config! :) No GitHub, well, it's gonna be a fun Friday...
Isn't it the whole idea of git to make user independent from place like github? After all if you have the repository on your local machine you can continue working as if nothing happened, right?
Yup. But the whole point of GitHub is to make you dependent on GitHub.
They've been slightly successful.
Re: DDoS Attack Against Dyn Managed DNS
#130Earlier quoted context omitted.
This is what you can do to restore your GitHub access: grep github ~/.ssh/known_hosts sudo vim /etc/hosts sudo killall -HUP mDNSResponder ping github.com
Why am I being downvoted for providing useful information? I don't understand HN...
Also probably the "hijacking top comment" part.
The other occurrence being here: https://news.ycombinator.com/item?id=12760156