How to protect your service (A-record question)?

S

sancho_panso2012-08-05 21:44:37

Domain Name System

sancho_panso, 2012-08-05 21:44:37

There is a domain: test.ru IN A 192.168.1.100
the service (DC hub) is spinning on the domain. Users who access the test.ru domain perfectly get to the hub and add it to their favorites.
There are bad guys who prescribe the A-record of the test.ru domain on their test2.ru domain,
i.e. it turns out as a result test2.ru IN A 192.168.1.100
and users entering test2.ru also get to the hub. But in the future, these bad guys change the A-record to their own and already have the n-th number of users who have added test2.ru to their favorites.
DC hub works on VerliHub over the domain, it can't listen (more precisely, it can, but in this case it's unacceptable)
How can I protect myself? any options are considered.

Reply

Answer the question

In order to leave comments, you need to log in

3 answer(s)

S

Sergey, 2012-08-06
@bondbig

No way.
No one will stop me, for example, from buying a google2.com domain and giving it any IP address.
In your situation, the problem lies here:

and users visiting test2.ru

why/why do they go to this domain?

K

korzunin, 2012-08-05
@korzunin

As far as I remember, in DC the domain name is not transferred from the client to the server, so without modifying the client, it is unlikely that anything can be done.

R

roginvs, 2012-08-06
@roginvs

You can just write a warning to users in MOTD