Sysadmins and those in the know, what is wrong with this picture?
% dig myspace.com
…
;; QUESTION SECTION:
;myspace.com. IN A
;; ANSWER SECTION:
myspace.com. 85833 IN A 216.178.32.50
myspace.com. 85833 IN A 216.178.32.51
myspace.com. 85833 IN A 127.0.0.1
myspace.com. 85833 IN A 216.178.32.48
myspace.com. 85833 IN A 216.178.32.49
Courtesy of OpenID and LID (emerging open-source Microsoft Passport replacements) guru Johannes Ernst.
No related posts.
{ 2 comments… read them below or add one }
DNS poisoning has turned into a massive plague in the last 6 months. People redirect domains to spam sites filled with overture/yahoo ads and then make profits off clicks.
LOL, maybe you just discovered the cause of their server errors that MySpace users complain about all the time.
Since they just added another IP to that list the 127.0.0.1 is probably just an admin’s error that is hard to fix because the records are cached world-wide. Such errors happen, about a year ago a whole top-level zone (.sk) was unreachable for several hours even when the cause was fixed immediately.
btw dating.corante.com is unreachable from here about 30% of time in last months