Hacker News new | ask | show | jobs
by thekos 4783 days ago
From the #linode IRC channel, caker (CEO) states it was a segfault in bind.

13:53:14 caker@ : They operate completely independently, other than loading from the same zones. This looks to be a segfault in bind itself

1 comments

Isn't having two independent name-servers supposed to prevent this kind of thing?
Appears that it cascaded across all of their nameservers. Seems like it could be an attack (remote or local DoS condition bug, since all users can create their own zones), or maybe just a random bug - hopefully they'll update us.
Weird!