Guides DNSSEC

What is DNSSEC?

How can you check where your website’s address came from? DNSSEC adds digital signatures to DNS answers. Learn how the check works and what your provider needs to arrange.

Someone visiting example.com first needs to look up the web server’s address. The answer needs to come from the right source and remain unchanged in transit. The company managing your domain settings can add digital signatures to the answers. This protection is called DNSSEC. A DNS service that supports validation checks the signatures before using the answer.

Check DNSSEC on your own domain

What changes for a visitor?

Without DNSSEC, a visitor looking up example.com receives an address but no digital signature for checking that answer’s origin. Ordinary DNS does have other safeguards.

With DNSSEC, the visitor’s DNS service can check the added signature. If it validates, the service can return the address. If the signature does not match the data, a validating DNS service normally returns an error instead of the answer. This makes forged DNS answers detectable. The visitor does not have to enter a key.

This concerns the DNS answer’s origin. It does not establish that the website’s owner is trustworthy. Signing a wrongly configured address does not make it the right address, and DNSSEC does not encrypt traffic to the website.

How the check reaches your domain

Your DNS provider signs the zone: the collection of records managed together. Each group of records gets a signature (RRSIG). A DS record in the parent zone holds a fingerprint of the corresponding public key. This creates a chain of trust from the DNS root through the parent zones to your data.

For example.com, that link is arranged through the company where you registered the domain: the registrar. It passes the required details to the operator of .com.

A validating DNS service checks the chain and signatures. If a required signature cannot be validated, the user normally receives an error (SERVFAIL) instead of the answer.

The records at a glance

  • DNSKEY: the public keys in your own zone.
  • DS: the fingerprint in the parent zone that refers to a key in your zone.
  • RRSIG: the signature covering a group of records.
  • NSEC/NSEC3: signed proof that a requested name or record is absent.

In everyday use, the DNS provider usually manages keys and signatures. Check with your provider and registrar who manages the DS link. If they are different companies, they need to coordinate changes.

Turning it on step by step

  • Check that your DNS provider supports signing and find out who maintains the DS link. One company may manage both automatically. Ask first.
  • Have the DNS provider sign and check the zone.
  • Need to submit the DS yourself? Copy all DS details exactly from your DNS provider’s instructions and enter them with the parent-zone operator, usually your registrar.
  • Allow for processing, then check the link and signing with your provider or a specialized tool such as DNSViz. Also check the DNS Radar result and test the website and mail.
  • Have the provider renew signatures and manage key changes automatically. Check again when moving or making a relevant change.

What DNS Radar does and does not establish

DNS Radar shows what the queried public DNS services report about DNSSEC. The scan does not verify digital signatures itself. An answer’s AD flag means that the DNS service reports successful validation. A name inside a signed zone can also carry that flag without having its own DS or DNSKEY record.

Read the result as follows:

  • Validation reported: a queried DNS service confirms a successful DNSSEC check for the answer.
  • DNSSEC records found, validation not established: keys or a DS alone do not prove that the chain works.
  • Not fully measured: a required query did not return a usable answer. This does not prove that DNSSEC is absent.

SERVFAIL can be a symptom of a DNSSEC fault, but it has other causes too. Ask the provider to investigate the DS/DNSKEY link, signatures and DNS answers, using DNSViz if helpful. Removing a DS does not immediately fix access for users who still cache the old value.

Why changes need coordination

If the DS link still points to an old key that the new zone no longer uses, the chain of trust can break. Validating DNS services may then be unable to provide a usable answer. The website and mail can become unavailable for their users.

This matters particularly when changing DNS provider, replacing keys or stopping signing. Have the providers coordinate the order and waiting periods. Changing a value in the registrar’s panel does not mean all public answers and caches have already changed.

Turning it off or moving safely

Do not stop signing while the parent zone or old caches still have a DS link that requires those signatures. The safe waiting period depends on the old DS TTL and processing at the providers involved.

If you really want to turn DNSSEC off:

  • First have the DS link removed from the parent zone.
  • Have the removal checked on the parent zone’s nameservers. Keep the existing signed zone working in the meantime.
  • Then wait at least until cached answers containing the old DS have completed their lifetime. Ask the provider to determine the period from the old DS TTL and any additional processing steps.
  • Only stop signing after that confirmed waiting period, then check DNS, the website and mail again.

When moving, prefer a procedure that keeps the chain of trust intact. Agree on it with both DNS providers and the registrar before switching. If that is not possible, a temporary move without DNSSEC may be needed. This interrupts DNSSEC protection and requires the same careful DS removal and waiting periods. Add the new DS only once the new signing works and old, incompatible data no longer interferes. No single number of hours is safe for every move.

Further uses: separate subzones and secure mail

For example.com, the DS link is usually arranged through your registrar into the .com zone. For a separately delegated zone such as team.example.com, the operator of example.com handles it. An ordinary subdomain within the same zone needs no DS link of its own.

DNSSEC is also needed for DANE/TLSA, which publishes the certificate or public key associated with a server. The DANE guide explains how this works for mail.

Primary sources

Frequently asked questions

Is DNSSEC mandatory?

Not for every domain on the internet. Sector or organizational requirements may apply. For Dutch government domains and relevant DNS resolvers, for example, Forum Standaardisatie describes a comply-or-explain requirement. Check the scope that applies to your organization. DNSSEC is also useful where forged DNS answers could cause harm, even without such a requirement.

What's the difference between DNSKEY and DS?

DNSKEY holds public keys in the signed zone. DS lives in the parent zone and refers to one of those keys. For a registered domain, you usually arrange that link through the registrar. For a separately delegated subzone, you arrange it through the parent-zone operator.

Does DNSSEC encrypt my DNS traffic?

No. DNSSEC proves an answer is genuine and wasn't changed along the way, but it keeps nothing secret: answers stay readable. For privacy of your DNS queries you use DoH or DoT.

Why is my domain unreachable after a provider switch?

An old DS that no longer matches the new signing is one possible cause. Have both providers check the DNS answers and chain of trust before changing settings. Repair the link through their migration procedure. If the DS must be removed temporarily, allow for processing and old DS caches. Access will not be restored everywhere immediately.

How do I check that DNSSEC works?

DNS Radar shows the queried DNS services’ reports, including AD for reported validation. For a fuller chain-of-trust check, use your provider’s validation or a tool such as DNSViz. Also test the website and mail after important changes. The scan does not make those connections for you.

Check DNSSEC on your own domain →