DNS, IP's and technical questions

llcstaff

Newbie
Joined
Jan 4, 2008
Messages
42
Reaction score
8
I've been upgrading some sites to a new server. One very old domain which used to show up in the serps (6 months ago) was given a new dedicated IP and DNS yesterday. I ran a trace route to see how fast it would propogate. To my surprise, the dedicated ip address was the old one but the final destination was a chicks with dicks dot com type domain name.

If the IP address is dedicated to my domain.... why does it resolve to a porn site in the trace route and not in the browser? Was this a configuration error at the host or did they resell my IP while telling me it was dedicated?

I realize this is probably a host company question but I'd like some outside thoughts on this. I doubt the host company will fess up to whatever the real cause of this is.
 
I've been upgrading some sites to a new server. One very old domain which used to show up in the serps (6 months ago) was given a new dedicated IP and DNS yesterday. I ran a trace route to see how fast it would propogate. To my surprise, the dedicated ip address was the old one but the final destination was a chicks with dicks dot com type domain name.

If the IP address is dedicated to my domain.... why does it resolve to a porn site in the trace route and not in the browser? Was this a configuration error at the host or did they resell my IP while telling me it was dedicated?

I realize this is probably a host company question but I'd like some outside thoughts on this. I doubt the host company will fess up to whatever the real cause of this is.

i believe your domain name resolution is resolved by your name servers (your authoritative servers) which during a recursive lookup will resolve the IP to your domain name (where your files are located). your DS servers does not answer to recursive lookups but will tell browsers which server to ask.

hence to find out the real IP of your domain, do a nslookup at the DS to see what that says.
 
Because it's usually one IP with many domain names. It's called a virtual host.
 
Sure sounds like the dedicated ip was really a shared ip( alot of hosts do this crap ) or your dns wasnt setup properly or wasnt propagated yet. When did you change the dns records and add the new ip at your registar? It can take up to 24 hours to propagate to the minor dns out there and is usually pushed to the major dns's in less than 4 hours
 
make sure the TTL in your DNS zone file is set low. sometimes they are set to take multiple days to change while you really just wanted an hour or so. it sounds like your host is having some kind of an issue if you're getting a porn site though....
usually they setup their http configuration to accept your domain as soon as it starts pointing to that ip.
either way, call your host and have them fix it.
 
Is it a Dedi, or at the very least VPS, if its shared hosting then dont even bother?

Update your ns ttl to 3600 from standard 84600. Then reboot BIND from the shell (not WHM or Plesk).

That should help the situation.

Cheers
aReJay
 
To answer the questions, this was a dedicated server and the domain was supposed to be on a dedicated ip using the host company name servers.

The domain propagated to the new name server last night and is now on it's own ip. The old IP when "trace routed" today, still displays the chicks with dicks domain name as the final destination.

I haven't heard back from the host yet but I will update this thread with their answer.
Tracert isn't a command I run alot since my only reason is to check connection times. In the end, I guess this is just another thing to keep an eye out for. Misconfigured dns or resold ip's that are supposed to be dedicated.
 
Back
Top