2 ms·
Pardon me if I'm just being dumb here, but the notion that DNS servers are two "lonely servers" seems totally wrong. They might be two IP addresses, but you can
by gfodor 17y ago
Pardon me if I'm just being dumb here, but the notion that DNS servers are two "lonely servers" seems totally wrong. They might be two IP addresses, but you can be damn sure DynDNS doesn't have two klunky duct taped together linux boxes on those IPs as the article would lead you to believe. To me their objectivity went out the window when they started that train of FUD.
My naive guess here is that twitter probably accidentally set really low TTLs on their root DNS entries on dyndns so some downtime on the dyndns servers due to a DDoS (the same kind of DDoS the article seems to say is not the root cause) caused the intermediate caches to all expire as well. DNS is designed to withstand these kind of outages if you configure it correctly since most DNS entries should be able to be cached for a damn long time. We use dyndns and set our public DNS entries to have a large TTL and internal dynamic IPs to be short TTL. EC2 elastic IPs make this really nice since we can swap out physical machines behind the elastic IPs without having to update any DNS at all.