DNSSEC and domain security: a look back at 2020

July 2020 marked ten years since the DNS root was first signed with DNSSEC. For someone running a website, the useful question was practical: could visitors trust the DNS answer that sent them to the server?

In its July 2020 explanation of DNSSEC, ICANN described how digital signatures let a validating resolver check that DNS data hasn’t changed since it was signed. That check helps protect the connection between a domain name and its intended destination. It doesn’t decide whose identity appears in the registration record.

Start with the job each service does

A private domain registration keeps personal details separate from the identity used to register a name. DNS directs visitors to services. Your hosting runs the website itself. Buying one of these services doesn’t automatically arrange the others.

For a small publication, that means the person choosing the domain should know who will manage its nameservers. If a developer handles DNS, give them a clear handover record and decide who approves changes. An anonymous customer account can still have an orderly maintenance process.

Before choosing a DNS provider, ask whether it supports the features your domain needs and who will manage them. Don’t assume a registration package includes DNSSEC administration because its description mentions protection.

A domain move needs a DNS plan

Changing hosts is easier when you have a record of the existing setup. Save the nameservers and the records used for the website and email. Agree when the new host should start receiving visitors, and keep the previous service available until you’ve checked the change.

If DNSSEC is enabled, ask the people managing the old and new DNS services to include it in the move. A rushed change can leave you paying for a working web server that visitors cannot reach. Treat the domain, DNS, and hosting work as one scheduled migration even when different companies provide them.

Where private registration fits

xUID lets you register .RU or .SU using a shared or private registration identity, then point the domain to your chosen hosting provider. You can keep an existing website host when you buy a new domain.

Full Bulletproof Protection adds an exclusive identity, priority support, and handling of abuse complaints within the service agreement. Ask separately about the DNS features and hosting work your project needs; that gives you a useful order specification before you pay.

If you’re preparing a move, keep the current configuration beside our nameserver and renewal guide and record who will make each change.