DNS Problem

arri

Registered
you'll have to take my word for it that i have no clue how i ended-up on this website...

i often open several google search-results in tabs in one window, especially when some sites respond slow. this was the case in this instance, and the above url had loaded in the last tab i reviewed for any usefull info. to my surprise, instead of usefull info (or porn), the tab was displaying the rootdir-contents of the locally running webserver.

for some reason 'free*********world.net' resolves into host 127.0.0.1
could anyone explain how this can happen?


i tried pinging the free********world.net from my server (remote debian machine) and that also resulted in respons from localhost there, so it's not related to some local dns/cache/router issues..

thanks,
arri
 
I wouldn't get involved, your email will be full of porn sites in a matter of days or so and get worse over a longer time...
 
This is probably how is has been coded in the DNS servers. Someone has reserved this name with the address 127.0.0.1. I don't see any reason for that, but that's the way it is. So anybody anywhere will get his own computer when using this address.
 
The DNS servers resolve correctly for the domain (looking strictly with DNS). Many times which sites are under attack, with will change their DNS to be 127.0.0.1 localhost causing the attacking machines to attack themselves.

If you continue to get this, you need to just keep checking your upstream dns servers to see where the problem is.

In terminal, type "nslookup", and then type "server x.x.x.x" with that being your DNS server. Then type in the name of the domain you want to lookup, if it comes back 127.0.0.1, then you know its your dns issuing it and you'd need to contact them and find out what this has been redirected, but I would wait at least 24 hours to see if it is a possible issue with TTL on the domain.
 
hi,

i'm sorry if i disturbed regular late-summer-sundayafternoon-business on this forum a bit..

after posting the original message yesterday i realised that having that url in the subject/title didn't exactly look very pretty in the forum-index view.
but then i discovered that while you can edit the text-body post-factum, the subject-line is untouchable.. (unless you're a mod or root i guess)

anyway, thanks for not killing the thread completely.

on topic;
DNS was the first i was thinking of, or maybe some script sending headers to redirect the browser to localhost. but with curl and wget i ended-up with the same dir-index-HTML from my local webserver, also after flushing caches/-dnsrecords/routing tables etc...
and as i wrote, also on my server the url would resolve into localhost.. while that machine is in a datacenter in another country, mostly minding its' own DNS-funk.. at least very unrelated to my local DNS-situation.

usually i completely ignore all the trickery, jackpot announcemnents, cheap lones and viagra sales.. i also don't understand how all that crap can work at all as a marketing strategy (and i don't care a bit)
but in this particular case i wanted to know the mechanics behind it.

i guess Scott must be right in that it's a DNS issue and is not to take very serious..let's see tomorrow.
but wouldn't expect one would be alowed to register a domain to resolve into localhost..

.a
 
Back
Top