Been there "suffered" that, although in my case it wasn't a porn site and I just served 301 "Moved Permanently" to any request for a page at the old domain.
I suggest if you have access to the configuration for your web server that you do a similar thing. If you don't want to serve a redirect (quite possible given that an old porn domain has got your IP) then look at virtual hosting, set-up a virtual host for the porn domain and just serve 404.
Trying to contact anyone to do anything about this sort of thing is fruitless. Email the technical contact at the whois record for the porn domain, tell 'em to delete any address records for the porn domain, and if that doesn't fix it nothing will.
[edited by: dmorison at 1:46 pm (utc) on June 13, 2003]
Can you IM or sticky the domain name? Hard to see what's actually going on without that.
I tried emailing Google and discussing the situation, they apparrently did not read the email thoroughly, they thought I was complaining about positioning and ranking.
I just wanted them to check and see if there was anyway to fix the actual url path.
Now everybody has that path..... and they get absolutely nothing in return.
This is really a bummer!
I thought about a 301 redirect, but I have an ethical problem with that. The domain is not mine to redirect. What if somebody else want's to buy that domain. They'll have the same problem I am having, their site would be continously pulling my site because of the redirect I've placed.
I also thought about having the IP changed, which I still may due because the problem is just not going away.
Anybody have opinions on changing the IP?
What kit are you running on?
Server type; do you have access to config files?
You can do something about it, but it will take time for Google to come around automatically.
I doubt there is anything they can do because it could be abused by people trying to get competitors sites taken out of the index.
Can you benefit from the traffic for the porn site in anyway?
|The domain is not mine to redirect. |
The IP address is yours to do what you want with - not your fault that porndomain.com resolves to your IP.
|What if somebody else want's to buy that domain. They'll have the same problem I am having, their site would be continously pulling my site because of the redirect I've placed. |
Agreed that they will have Google indexing your site at first, but that is happening all the time now as domains are expiring and new owners are buying them up.
A new owner coming along would sort out the resolution problem however, because the registrar would _have_ to set-up the record for the new owner, and that would almost certainly be provided by a different ISP and therefore DNS server(s).
[edited by: dmorison at 1:59 pm (utc) on June 13, 2003]
No, not really.
The did not renew the domain and their site no longer exists so all you get are DNS errors. So nobody can see any content.
Last time I checked Porn sites and Outfitters weren't a very good mix at least since they made the move "Deliverance"
;) need a little sense of humor right now.
I'm with dmorison. I'd get in there with a 301 to your domain. Besides, If someone did light that domain back up, it would work itself out - they wouldn't be stuck with your content.
I bet it'll be gone in a couple of months, anyways.
I agree about the IP address, but are you telling me that I should place a redirect against the actually IP address for example;
##.###.##.### 301 redirect to www.mydomain.com
I hadn't thought of that I was thinking about;
www.pornsite.com 301 redirect to www.mydomain.com
Can I do that?
A couple of months is a little late for the outfitting business. They need the site working now for bookings in the fall. That's my problem.
But your site is working - yes?
The only "problem" now is that the site has got indexed under porndomain.com.
How does the listing rank for the keywords that people might use to find your site?
If it ranks highly you're onto a winner, because unless you're in the world's least competitive market it is going to take you a while to get your new site to Page 1 of the search results anyway.
Yes, were up their in the ranking on our keywords, but wont people get discourage when the click the link and end up with a DNS error?
Or are you telling me to do the 301 and then it wont'be a problem?
It's Friday the 13th and I am so confused!
|I called our webhost and they said that we would have to contact the registrar of that domain and get it straighted out. |
This is BS - if you have the domain with the name servers correctly listed - it is the hosts fault.
I have had this happen dozens of times with at least three different hosts.
EVERY time it is the hosts fault.
Sticky me the domain if you'd like.
I'd bet $10 that a tracert will end up at your host - or whoever you have as the dns.
|This is BS - if you have the domain with the name servers correctly listed - it is the hosts fault. |
I don't think that's the problem. Another domain, nothing to do with his host or registrar is resolving to his IP...
The site is resolving fine now (he stickied me the domain name), but google had indexed porno site at his IP address.
Pornosite no longer resolves - so it shouldn't be the problem the next time googlebot comes around.
Google wasn't indexing his site incorrectly - they were indexing the porno site incorrectly (which was either their fault for caching the DNS too long - or the hosts).
I have had hosts mess this up many times (unfortuantely). I can't say for sure who messed it up - but it wasn't the registrar. Most of the time I have seen this happen it is the host.
I have a site right now (hoepfully it is fixed by now) if you go to the site - someone elses pages show up. This is because the moronic people I paid $$$$ for my host can't figure out how to set up their DNS records.
Basically the host sets up two domains to go to the same IP address. The registrar doesn't keep track of your IP - it keeps track of your hosts DNS computer. Apparently you have to be a rocket scientist to set these up - as I keep getting hosts who have my domains go to other people pages.
It usually only takes someone a second to fix it, but someone has already fixed it - if it was the hosts fault. So it should be fine when googlebot comes around.