Twitter lost control of its DNS records on Dec. 17 for about an hour, but the effects lasted a bit longer due to DNS caching. While neither Twitter nor their registrar DynDNS, is saying much other than that the DNS records were changed at around 10pm PST, there has been ample speculation that the perpetrators got control of administrative credentials for Twitter.com.

Go to Source

Popularity: unranked [?]