A record of domain / Abuse?

Good evening. A touchy subject, how to defend and act?
The essence of the story: Today I found that my website And fully displayed on another domain B. At first I thought, maybe the website was stolen... but not able to log into the domain B viewed phpinfo is my server. Then looked at WHOIS domain was NS address hosting jino. Those. support was given to understand that the jino people have pointed the A record ip address of the server, and it is necessary to apply directly to the host. Wrote abuse them, waiting for an answer... probably in MON the answer will come.

The domain B in the google index 400+ pages... my domain And loss of positions and pages.

Question: How to confront such lawlessness? and what to do? For the first time faced with such a case.
October 8th 19 at 01:20
6 answers
October 8th 19 at 01:22
To tell the server (apache?), he doesn't respond your website on any domain, and only responded to yours, then the problem itself will disappear.
and in robots.txt it is useful to specify a domain, then the search engines will assume your domain is the main villain and stick together with your - Alyson.Hess commented on October 8th 19 at 01:25
October 8th 19 at 01:24
RewriteEngine On<br> RewriteRule ^([nameunit]*)$ /шлинах.html [L]<br>
Better:

RewriteEngine on<br> RewriteCond %{HTTP_HOST} ^*choroidal.Yong$<br> RewriteRule ^(.*)$ <a href="http://свойдом.ен/">svoydom.Yong/</a>$1 [R=301,L] - Alyson.Hess commented on October 8th 19 at 01:27
But nginx seems to be something like this:

server {<br> server_name .choroidal.Yeon;<br> rewrite ^ <a href="http://свойдом.ен">svoydom.Yong</a>$request_uri? permanent;<br> } - reina_Nitzsche65 commented on October 8th 19 at 01:30
No, nginx will be like this:

server {
 listen 80;
 server_name www.youdomain.tld www.alias.tld alias.tld;
 ## if nginx >= 0.9.1
 return 301 $scheme://youdomain.tld$request_uri;
 ## else
# rewrite ^ $scheme://youdomain.tld$request_uri permanent;
}
- reina_Nitzsche65 commented on October 8th 19 at 01:33
October 8th 19 at 01:26
the decision on pichai
if !($_SERVER['SERVER_NAME'] == 'VISIT') {<br> exit();<br> }
Sori for the second comment, wrote in haste.
Even in this error. - Alyson.Hess commented on October 8th 19 at 01:29
October 8th 19 at 01:28
the decision on pichai
October 8th 19 at 01:30
The correct code along with S1eng:
<?php if ($_SERVER['SERVER_NAME'] != 'domain') {
exit();
}?>
<?php $_SERVER['SERVER_NAME'] != 'domain' && die(); ?> - Alyson.Hess commented on October 8th 19 at 01:33
Tyra, you are still in the database, do something to redirect. The problem is solved in the most direct way a normal VirtualHost setting in Apache or with nginx server_name Directive. It is not necessary to use a wildcard, the whole business. - reina_Nitzsche65 commented on October 8th 19 at 01:36
And this is absolutely the wrong approach. Must vozvrat 301 code to help search engines to understand where the main domain, and where not. Gluing, sir - reina_Nitzsche65 commented on October 8th 19 at 01:39
bondbig: well, this method can be useful if the virtual hosting — no access to the settings of the web server. - Kirstin.Corkery commented on October 8th 19 at 01:42
October 8th 19 at 01:32
You can still do better.
for example, we did
Example: womansocset.ru
This domain does not belong to us, but the owner of that domain decided to do us the nasty. Now it shows OUR domain ad banner.

All you can find benefit )))
original :) - Alyson.Hess commented on October 8th 19 at 01:35

Find more questions by tags Domain names market