On Friday 06 August 2010 21:44:15 Arun Khan wrote:
On Fri, Aug 6, 2010 at 4:52 PM, Dattatray Kamble meet2dsk@gmail.com wrote:
***** Can you not spend a few moments to trim out unnecessary text and make your posts more readable?*****
OK .. i start once again..
- www.hesco-fl.com ...is our production site ( users may misspell
it as www.hesco-lf.com ..&..get redirected to ..PORN site..( raunchy king of porn site.....single site )
- problem occurs on Fedora 10, Centos 5.4, Windows Vista
Business, RHEL-5.
Do all of the above systems have 202.148.202.4 as the DNS server in /etc/resolv.conf or the Windoze equivalent?
** server can't find hesco-lf.com: NXDOMAIN
I get the same result.
[root@sydomain ~]# tracert hesco-lf.com
Have you aliased traceroute to tracert? just curious.
it's done by default, tracert = traceroute -I
traceroute to hesco-lf.com (208.76.179.25), 30 hops max, 40 byte packets
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^Hmmm. for some reason the OS resolver on your system is resolving the non existing domain "hesco-lf.com" to 208.76.179.25.
Reverse map of 208.76.179.25 turns out to spider.ten.com.
$ host 208.76.179.25 25.179.76.208.in-addr.arpa domain name pointer spider.ten.com.
http connection to spider.ten.com "appears" to be redirected to the raunchy site http://kingofporn.com/ but ....
$ host kingofporn.com kingofporn.com has address 208.76.179.25
What I don't understand is -- why/where do the respective host OS "resolver" translate a non-existent domain name into an IP number 208.76.179.25?
My guess is he's got a dns server on a hosed doze box on his network.