3 ms·
You haven't posted the real domain so I can't check but try pinging the clone's domain and make sure it isn't pointing to your server's IP. It may just be a dom
by kaolinite 11y ago
You haven't posted the real domain so I can't check but try pinging the clone's domain and make sure it isn't pointing to your server's IP. It may just be a domain that belonged to the previous owner of your server's IP.
- codepeach 11y agoYep, good point - and quite likely if your website is on it's own (non-shared) IP address. One way to work around this would be to create a .htaccess file to redirect any requests not matching your domain name to your own :)
- hbhakhra 11y agoReal domain is kmsurvival.com. Your guess were correct, pinging the fake domain did return our ip address. I will go ahead and put in the redirect in the .htaccess file.
- quesera 11y agoI always run a null default virtual host, which serves no content and logs no traffic (or maybe logs to a default-access.log). It deflects a lot of blind security attacks..all of which would fail of course, but I don't need that noise in real log files. This would solve your problem too. If you're feeling vindictive, redirect requests for the offending domain somewhere that will be bad for their SEO. EDIT: I should add that a null default vhost will exclude HTTP/1.0 clients. But that's a non-issue unless you're serving to very old embedded systems.