Sometimes, when it’s late at night in the office, we notice odd things in the DNS that don’t belong. Sometimes they’re worthy of a blog mention. Tonight we highlight a myspace.com DNS misconfiguration.
$ host -vv myspace.com
Trying “myspace.com”
;; ->>HEADER< <- opcode: QUERY, status: NOERROR, id: 24145
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;myspace.com. IN A
;; ANSWER SECTION:
myspace.com. 68350 IN A 216.178.32.51
myspace.com. 68350 IN A 216.178.32.50
myspace.com. 68350 IN A 216.178.32.49
myspace.com. 68350 IN A 216.178.32.48
myspace.com. 68350 IN A 127.0.0.1
Received 109 bytes from 208.67.222.222#53 in 9 ms
For those of you who don’t know, 127.0.0.1 is another way of saying localhost which is another way of saying your computer. So while that may literally take me to My Space (as in, my personal computer), it is certainly not going to get me to the website myspace.com. Whoops.
Tagged with:
Pingback: .: blogging augusto :.
Pingback: blabberz » Myspace DNS Hilarity!
Pingback: MikleFedorov.com
Pingback: Tuesday Link Dump » Various and Sundry
Pingback: Tuzworld » Archive » myspace.com = 127.0.0.1?
Pingback: myspace.com = 127.0.0.1? « An Interesting Point
Pingback: 2006.11.01 Daily Security Reading « Rodney Campbell’s Blog
Pingback: James Kirsop [dot] com » Archives » Hey MySpace.com - we can’t reach you on 127.0.0.1
Pingback: Myspace DNS Problems, Offline by Elliott Back
Pingback: Bitperbit » MySpace y el error de sus DNS
Pingback: » myspace.com = 127.0.0.1? - Haiku Headlines | Headlines of Today. In 17 syllables. What more do you need?