DNSSEC adds cryptographic verification to DNS responses, helping resolvers detect forged or altered records. This practical checklist explains what DNSSEC does, when to enable it, how to publish a DS record safely, how to test validation, and how to troubleshoot failures without making a domain unreachable.
Overview
DNS was designed to locate services, not to prove that every response is genuine. DNSSEC, short for Domain Name System Security Extensions, adds a chain of trust to DNS. A validating resolver can use that chain to confirm that an answer came from the authoritative DNS service and was not modified in transit.
DNSSEC does not encrypt DNS traffic. It also does not replace TLS, an SSL certificate, secure registrar access, or good account security. Instead, it helps protect the authenticity and integrity of DNS data. That makes it relevant for websites, email services, APIs, identity systems, and other infrastructure that depends on accurate domain records.
The most important operational principle is that DNSSEC must be configured as a complete chain. The authoritative DNS provider signs the zone and publishes DNSKEY and RRSIG records. The domain's parent zone receives a DS record that identifies the trusted key. If the DS record and the DNSKEY records do not match, validating resolvers may return SERVFAIL rather than the expected DNS answer.
DNSSEC is usually managed in two places: the DNS provider, where signing and key management occur, and the registrar, where the DS record is added or removed. Some providers combine both functions in one control panel. Before making changes, confirm which system is authoritative for the domain and whether it supports DNSSEC signing and DS record management.
DNSSEC record reference
| Record | Purpose | Where it is normally managed |
|---|---|---|
| DNSKEY | Publishes a public signing key for the DNS zone. | Published by the authoritative DNS provider. |
| DS | Delegates trust from the parent zone to a child zone by identifying a DNSKEY. | Added at the registrar or domain management provider. |
| RRSIG | Contains signatures for DNS record sets. | Generated and published by the signing DNS provider. |
| NSEC or NSEC3 | Provides authenticated proof that a DNS name or record does not exist. | Generated by the signing DNS provider. |
Checklist by scenario
Before enabling DNSSEC
- Identify the authoritative nameservers. Check which nameservers the parent zone delegates to. DNSSEC must be enabled on the provider that actually hosts the authoritative zone.
- Confirm provider support. Look for DNSSEC signing, DS record entry, key-rollover support, and documented recovery steps. The available algorithms and digest options can vary by provider and registry.
- Record the current configuration. Export or document A, AAAA, CNAME, MX, TXT, and other important records. DNSSEC should not change ordinary DNS answers, but a rollback plan is useful if a configuration error occurs.
- Check delegation and zone health. Resolve the domain from more than one network and verify that nameservers answer consistently. Fix missing records, lame delegation, or intermittent authoritative responses first.
- Confirm access to both control panels. You may need the DNS provider to generate signing information and the registrar to publish the DS record.
How to enable DNSSEC safely
- Open the DNSSEC or zone-signing area at the authoritative DNS provider.
- Enable signing or create the provider's DNSSEC configuration. Follow its instructions for algorithm, key tag, digest type, and digest value.
- Copy the DS details exactly. Treat the key tag, algorithm, digest type, and digest as structured values; do not add spaces, alter capitalization where the panel is case-sensitive, or substitute a DNSKEY value for a DS digest.
- At the registrar, add the DS record under the domain's security or DNSSEC settings. Some panels ask for separate fields; others accept a complete DS record.
- Wait for the parent-zone delegation and resolver caches to update, then test from an independent validation tool and from the command line.
- Keep a change record containing the date, provider, DS values, and the person or system that made the change.
Do not add a DS record before the authoritative DNS provider is ready to serve the corresponding DNSKEY and signatures. Conversely, do not remove DNS signing while leaving a DS record published. During a migration, coordinate the order of operations with both providers so that the chain remains valid.
During a registrar or DNS provider migration
- Inventory the existing DS record and DNSSEC keys before changing nameservers.
- Build and test the new zone at the destination provider before switching delegation.
- Follow the destination provider's DNSSEC migration instructions rather than assuming that keys can be copied unchanged.
- Plan the DS transition. A stale DS record at the parent is a common cause of validation failure after a nameserver change.
- Use a rollback plan that explains which DS record, nameserver delegation, and zone data should be restored.
During a key rollover
- Confirm whether the provider performs an automatic rollover or requires manual DS changes.
- Verify that the new DNSKEY is published and available before retiring the old key, following the provider's timing guidance.
- Check that the parent DS record identifies an active key and that signatures can be validated with the published key set.
- Do not delete an old key or DS record simply because a new one exists; the correct overlap and removal sequence depends on the rollover method.
- Re-test after each stage and save the resulting DNSSEC status.
What to double-check
Use more than one test method. A browser reaching a website does not prove that DNSSEC is valid because some resolvers do not validate DNSSEC or may have cached an earlier answer.
For command-line checks, dig can request DNSSEC data and the validation status:
dig example.com A +dnssec
dig example.com DNSKEY +dnssec
dig example.com DS +dnssec
Look for DNSKEY, RRSIG, and DS data where expected. With a validating resolver, the response's authenticated-data indicator may appear as ad when the answer has been validated. Results depend on the resolver used, so compare with an independent DNSSEC analyzer or validation checker.
Also check the complete path:
- The parent zone publishes the intended DS record.
- The child zone publishes the DNSKEY referenced by that DS record.
- RRSIG records cover the relevant record sets and remain within their validity period.
- Nameservers listed at the parent serve the same signed zone.
- Authoritative responses are consistent across all nameservers.
- Mail records, subdomains, and verification TXT records still resolve normally.
DNSSEC troubleshooting decision tree
Does a validating resolver return SERVFAIL? First query the domain through more than one resolver. If only one resolver fails, investigate resolver-specific caching or behavior. If multiple validating resolvers fail, continue through the chain.
Is a DS record published at the parent? If yes, confirm that its key tag, algorithm, and digest match an active DNSKEY in the child zone. A mismatched or stale DS record is a leading cause of DNSSEC validation failure. If no DS record is published, the domain may be insecure rather than broken; confirm that the DNS provider is actually signing the zone and that the intended security state is clear.
Does the child zone publish DNSKEY and RRSIG records? If not, signing may be disabled, incomplete, or active on a different DNS provider. Check the authoritative nameservers and the provider's DNSSEC status.
Are only some nameservers failing? Compare authoritative responses individually. An unsynchronized or unsigned nameserver can make validation intermittent. Correct the zone or delegation before changing DS records.
Did the error begin after a migration or rollover? Review the change sequence. Look for a DS record left at the old key, a new key not yet published, or a signing service that was disabled too early. If you cannot restore a valid chain promptly, follow the registrar and DNS provider's documented emergency recovery procedure rather than making repeated ad hoc changes.
Common mistakes
- Confusing DNSKEY and DS values: the DS record contains a digest of a DNSKEY, not the public key text itself.
- Editing the wrong provider: changing records at a DNS dashboard that is not authoritative has no effect on live DNS.
- Adding DS too early: publishing a DS before the signed child zone is ready can make the domain fail validation.
- Removing DS too late: turning off signing while the parent still expects a signed child can produce SERVFAIL.
- Ignoring all nameservers: one stale or unsigned authoritative server can break validation even when another server looks correct.
- Testing only in a browser: browser success may reflect caching or a non-validating resolver.
- Treating DNSSEC as a replacement for SSL: DNSSEC helps authenticate DNS data; it does not provide encrypted web traffic. For certificate guidance, see how to install and renew an SSL certificate on cloud hosting.
Keep DNSSEC changes separate from unrelated DNS edits where possible. If a website launch, email migration, or nameserver change is happening at the same time, record each change independently. The DNS records reference can help verify ordinary records, while the domain transfer checklist covers broader migration planning.
When to revisit
Review DNSSEC during quarterly DNS security audits and before planned seasonal infrastructure changes. Revisit it immediately when you change registrars, move authoritative DNS, replace DNS software, alter key-management procedures, or receive a validation alert. It is also worth checking after a major provider control-panel change or a documented update to registry, registrar, or DNSSEC policy.
Use this short recurring checklist:
- Run an external DNSSEC validation test and save the result.
- Compare the published DS record with the active DNSKEY set.
- Check every authoritative nameserver for consistent signed responses.
- Confirm that website, email, API, and verification records still resolve.
- Review upcoming registrar renewals, migrations, and key-rollover dates.
- Update your DNS change log and recovery contacts.
DNSSEC is most useful when treated as an operational control rather than a one-time switch. A documented chain, independent validation, and a tested rollback plan make domain security easier to maintain when providers, workflows, and DNS infrastructure change.