% whois twitter.com
[...]
Record expires on 21-Jan-2018.
Record created on 24-May-2009.
Database last updated on 18-Dec-2009 01:36:19 EST.
Domain servers in listed order:
NS3.P26.DYNECT.NET
NS2.P26.DYNECT.NET
NS1.P26.DYNECT.NET
NS4.P26.DYNECT.NET
% host twitter.com NS1.P26.DYNECT.NET
Using domain server:
Name: NS1.P26.DYNECT.NET
Address: 208.78.70.26#53
Aliases:
twitter.com has address 66.147.242.88
twitter.com mail is handled by 10 aspmx.l.google.com.
twitter.com mail is handled by 20 alt1.aspmx.l.google.com.
% host twitter.com
twitter.com has address 74.217.128.160
twitter.com mail is handled by 20 alt1.aspmx.l.google.com.
twitter.com mail is handled by 10 aspmx.l.google.com.The traceroutes, of course, lead off to entirely different directions. The best part is that the server they, um, borrowed couldn't begin to handle the twitter load, so they've kind of DDOSed themselves.
eta: Courtesy whoever this is, a screenshot resaved locally here.
eta2: See also Fandom Lounge.
eta3: They really didn't plan this well; they didn't even manage to set up all the servers they wanted to use.
eta4: Well, that didn't take long. Back up. But:
% whois twitter.com
[...]
Record expires on 21-Jan-2018.
Record created on 24-May-2009.
Database last updated on 18-Dec-2009 02:23:20 EST.
Domain servers in listed order:
NS3.P26.DYNECT.NET
NS2.P26.DYNECT.NET
NS1.P26.DYNECT.NET
NS4.P26.DYNECT.NET
Seriously? Are you shitting me? The hax were so lame that this is all it took? Oh man, somebody is so fired.
eta5: Over on metafilter, people are speculating about mass password grabs, and I don't want to diss that possibility, but I don't think they appreciate how quickly (and spectacularly!) the lamehax servers fell over, and how at least one of them didn't even get set up right (see eta3).
