E
E
Eugene2013-01-13 00:10:45
Nginx
Eugene, 2013-01-13 00:10:45

Domain spoofing - NS spoofing, how to treat?

Greetings! I hope you can help:
There is a server 93.170.48.61 and sites are located on it, now there is a substitution for 31.170.179.200
ww6.testtradedoubler.com -> from there it is already a redirect to
my other NS sites, the files are not infected ...
but now for 2 hours pings from PCs are different:
Below in the comments I give an example .
Unfortunately, I don’t administer the server (I don’t have skills), please tell me how to prohibit substitution?

Answer the question

In order to leave comments, you need to log in

3 answer(s)
T
truekenny, 2013-01-13
@CB9TOIIIA

You have only NS servers in the whois of the domain, and there are left (ns ? .tymo se nko-vona.com) NS records on them.
Probably, sometimes the DNS client trusts one data, sometimes others - load balancing.
Fix NS records on your NS servers.

V
Vlad Zhivotnev, 2013-01-13
@inkvizitor68sl

[email protected]:~$ host -t NS tymoshenko-vona.com
tymoshenko-vona.com name server ns2.tymosenko-vona.com.
tymoshenko-vona.com name server ns1.tymosenko-vona.com.
Are the NSs yours?

A
alexdob, 2013-01-13
@alexdob

Server:         8.8.8.8
Address:        8.8.8.8#53

Non-authoritative answer:
Name:   tymoshenko-vona.com
Address: 93.170.48.61

what is the problem? who replaces whom?

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question