Security precautions: Server cache poisoning and domain name hijacking

The problem of domain spoofing is an important part of the organization. Not long ago, there were hackers who defrauded customer service representatives to modify the IP address of Hushmail's primary http://www.aliyun.com/zixun/aggregation/13351.html "> Domain name server." For the moment, Hushmail's CTO Brian Smith has been furious, and it's really annoying that hackers are so gullible about their domain registrar's customer service representatives.

"It really sucks for us," Smith said. I would like to see registrars develop and publish better security policies. However, I could not find a registrar to do so, since this incident, I have been looking for such registrars. ”

Panix.com president Alex Resin also felt the same strong dissatisfaction with the Panix domain name hijacked in January this year as a result of the Registrar's problems. First, his registrar sold his domain registration to a reseller without prior notice. The reseller then shifted the domain name to a social engineer-without notifying resin.

Resin said: "The domain Name system needs systematic, fundamental reform." There are a lot of suggestions now, but things are not moving fast enough. ”

Waiting for market demand and the ICANN leadership to force registrars to implement a safe transfer policy will take a long time. Therefore, Resin, Smith and ICANN's Chief Registrar liaison officer, Tim Cole, presented the following risk reduction recommendations:

1. Ask your registrar to come up with a written, enforceable policy statement. If you need to transfer the domain name, ask them to contact you in time with the terms of the written document.

2, lock the domain name, require the Registrar to unlock the password or other identity information before allowing the transfer.

3. Keep the official contact information of the Registrar in the current state.

4. Choose the Registrar who provides 24x7 service so that they can act quickly in case of violation.

5. If an unauthorized transfer occurs, contact the registrar immediately.

6. If your problem is not resolved, go to your Domain name registration authority (for example, VeriSign is responsible.) COM and. NET registration).

7. If you still encounter problems when you get your domain name back, contact ICANN (transfers@ICANN.org).

8, if you have a large domain, like Google, be your own registrar or your own reseller, using Tucows.com's open Api,opensrs to control all your domain names.   &NBSP