Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Massive Dyn DNS outage

news.ycombinator.com

Post reply on HN
Print view View original

121–130 of 302 posts

Re: Massive Dyn DNS outage

#124

Post by jbaviat »

Issue came from dynect.net:

  $ dig +trace github.com

  ; > DiG 9.8.3-P1 > +trace github.com

  [...]

  ;; Received 488 bytes from 192.228.79.201#53(192.228.79.201) in 154 ms

  github.com.		172800	IN	NS	ns1.p16.dynect.net.
  github.com.		172800	IN	NS	ns3.p16.dynect.net.
  github.com.		172800	IN	NS	ns2.p16.dynect.net.
  github.com.		172800	IN	NS	ns4.p16.dynect.net.

  ;; Received 178 bytes from 192.42.93.30#53(192.42.93.30) in 54 ms

  ;; connection timed out; no servers could be reached

Re: Massive Dyn DNS outage

#125

Post by crgwbr »

DNS came back for a while and just started flaking again.

  $ nslookup github.com
  ;; Got SERVFAIL reply from 8.8.8.8, trying next server
  Server:     10.0.0.1
  Address:    10.0.0.1#53
  
  Non-authoritative answer:
  Name:   github.com
  Address: 192.30.253.112
  
  $ nslookup twitter.com
  ;; Got SERVFAIL reply from 8.8.8.8, trying next server
  ;; Got SERVFAIL reply from 8.8.4.4, trying next server
  Server:     10.0.0.1
  Address:    10.0.0.1#53
  
  Non-authoritative answer:
  Name:   twitter.com
  Address: 199.16.156.102
  Name:   twitter.com
  Address: 199.16.156.230
  Name:   twitter.com
  Address: 199.16.156.198
  Name:   twitter.com
  Address: 199.16.156.70

Re: Massive Dyn DNS outage

#126

Post by jorts »

jbaviat wrote: post #124

Issue came from dynect.net: $ dig +trace github.com ; > DiG 9.8.3-P1 > +trace github.com [...] ;; Received 488 bytes from 192.228.79.201#53(192.228.79.201) in 154 ms github.com. 172800 IN NS ns1.p16.dynect.net. github.com. 172800 IN NS ns3.p16.dynect.net. github.com. 172800 IN NS ns2.p16.dynect.net. github.com. 172800 IN NS ns4.p16.dynect.net. ;; Received 178 bytes from 192.42.93.30#53(192.42.93.30) in 54 ms ;; conne…

They're investigating now: https://www.dynstatus.com/incidents/nlr4yrr162t8

Re: Massive Dyn DNS outage

#129

Post by charles98102 »

mancerayder wrote: post #119
6d6b73 wrote: post #32

All this talk about redundancy, real-time apps, scalable architecture and and a "simple" DDOS against DNS architecture brings half of the internet down. Honestly did nobody think about having a spare dns at some other company? or even backup dns server exactly for a situation like that?

If ONLY they had 10X developers ... EDIT: joking aside, the issue with multiple DNS providers is primarily (in my experience at the company I'm at having investigated this in the past) intelligent DNS entries. Example, 'return these A records, in this order, based on the number of requests, roughly balanced'. There's no universal standard, just common aspects. DNS Provider A has one set of features, names for returni…

+1
Post reply on HN