391–400 of 721 posts
It is spreading to other DNS providers, too: https://status.fastly.com/ www.ft.com is unreachable for example.
I'm a GitHub employee and want to let everyone know we're aware of the problems this incident is causing and are actively working to mitigate the impact. "A global event is affecting an upstream DNS provider. GitHub services may be intermittently available at this time." is the content from our latest status update on Twitter ( https://twitter.com/githubstatus/status/789452827269664769 ). Reposted here since some peo…
I'm curious why you don't host your status page on a different domain/provider? When checking this AM why GitHub was down, I also couldn't reach the status page.
Very funny guys, can you stop now? We have a demo in 4 minutes.
How did the demo go?
Earlier quoted context omitted.
Presumably with something like `dig @208.67.220.220 -t CNAME .herokussl.com`. This uses the OpenDNS nameservers, that people have been reporting as working. Haven't tested it as I am on the go.
thanks! figured it out but appreciate the help!!
Earlier quoted context omitted.
thanks! figured it out but appreciate the help!!
I'm seeing "connection timed out; no servers could be reached". Anyone else seeing that when trying to run the above command?
208.67.222.222 208.67.220.220
(or specify dns server in the command)
Switch to OpenDNS servers - 208.67.222.222 and 208.67.220.220. Even google NS are down it seems. Heroku works after switching to opendns.
Earlier quoted context omitted.
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 know a lot about some things, but almost nothing about networking, so excuse me if this is a really dumb question but - would your physical location determine what hosts you returned from that query? Like if you were in Asia would you get different ones back?
I thought DNS (particularly public) was basically immune to DDoS? If one DNS server is down, use the cached result or another server. DNS is some of the most distributable, cachable data I can imagine.
I used to work for a DNS/DDoS provider, and this was a very real problem. Leave the PoPs that are being affected out, or risk overloading the other PoPs by overloading real traffic.
Before moving the other traffic, you also have to worry about blocking the DDoS traffic otherwise you're just redirecting them to the other PoPs. Mitigating DDoS attacks are not fun, and hard to block.
Earlier quoted context omitted.
If your DNS server is offline, is the last record it returned when it was online really the "wrong" one? There'd be no right one in that case.
Exactly. You can't know if it is still valid, so you might send clients to an IP that's now controlled by somebody else. Worst case, they know and set up a phishing site. DNS generally has been reliable enough that the trade-off is not worth it.
They'd need to specifically gain access to the last known good IP address, which might be different depending on which DNS resolver you talk to (geodistribution, when the record was last updated, etc). I wouldn't really consider that a realistic attack vector.