To enable DNSSEC validation for your zone, sign the zone so it publishes DNSKEY and RRSIG records, then publish a matching DS record at the parent through your registrar. Resolvers can then verify each answer from the root down. Missing or broken links in that chain trigger a high-severity finding.
DNSSEC is a set of DNS extensions that lets resolvers verify answers with digital signatures. The architecture is defined in RFC 4033, and the record formats and validation procedure in RFC 4035.
What triggers this finding?
The scanner expects an unbroken chain of trust with three links:
- DS at the parent. The registry for your TLD publishes a hash of your key-signing key.
- DNSKEY in your zone. This is the key the DS record points to.
- RRSIG over your answers. A resolver checks these signatures against the DNSKEY.
The finding fires when any link is absent or inconsistent. Common causes:
- The zone was never signed, so there is no DNSKEY and no RRSIG.
- The zone is signed but nobody uploaded a DS record to the registrar.
- A DS record exists but matches no current DNSKEY, often after a provider migration or key rollover.
- Signatures have expired because automatic re-signing stopped.
The third and fourth cases are worse than having no DNSSEC at all. Validating resolvers answer SERVFAIL, and your domain disappears for their users.
Why is a missing chain of trust rated high?
Plain DNS answers are unauthenticated. An attacker who can race a response, poison a resolver cache, or sit on the path can substitute records, and the resolver has no way to notice. DNSSEC gives resolvers a way to notice.
The severity is high because other controls rest on DNS. CAA records limit which CAs may issue certificates. MTA-STS discovery depends on DNS records. TLSA records pin certificates for mail transport. If the answers carrying these controls can be forged, they are advisory only. An attacker who forges them can strip your mail protections or obtain a certificate for your name. The cost to an organization is misdirected mail, intercepted credentials, and an audit finding that undermines every DNS-based control you claim.
For the same reason, a TLSA record in an unsigned zone offers no protection. See why TLSA records need a DNSSEC-signed zone.
How do I enable DNSSEC validation for my zone?
Start with your DNS provider. Managed providers usually offer a one-click signing option that creates the keys and handles re-signing. Self-hosted servers need a signing policy. In recent BIND versions, a dnssec-policy statement on the zone enables automatic key management. Exact syntax varies by server and version, so check your server's documentation.
After signing, retrieve the DS record data to give to the registrar:
dig +short DNSKEY example.com
dig +short DS example.com @a.gtld-servers.net
Your provider or signing tool will usually print the DS values directly. A DS record has four fields: key tag, algorithm, digest type, and digest.
example.com. 3600 IN DS 12345 13 2 49FD46E6C4B45C55D4AC49FD46E6C4B45C55D4AC49FD46E6C4B45C55D4AC1234
Then add the DS record in your registrar's control panel. If the registrar and DNS provider are the same company, there may be a single toggle. If they differ, you must copy the values across manually. For the registrar step, see how to fix a missing DS record at the parent.
Order matters. Publish a signed zone first and confirm it validates, then add the DS record. Adding the DS before the zone is signed correctly breaks resolution.
Avoid common pitfalls
- Keep the DS record in sync during provider migrations. Before moving a signed zone, plan the key handover, or temporarily remove the DS record and accept a window without DNSSEC.
- Make sure every authoritative nameserver serves the same signed data. A single unsigned secondary produces intermittent failures.
- Monitor signature expiry. Signing automation can fail silently, and RRSIG records carry an explicit end date.
- Check delegations too. A stale glue record can send resolvers to the wrong servers, as covered in fixing DNS glue mismatches.
How does the scanner detect and rate this?
The check queries the parent for a DS record, queries your authoritative servers for DNSKEY, and requests answers with DNSSEC data so it can inspect the RRSIG records. It then walks the chain the way a validating resolver does, following the procedure in RFC 4035. SetEnforce checks that the DS digest matches a published DNSKEY and that signatures over the answers verify and have not expired.
The finding is rated high whenever the chain is incomplete or broken. The attached evidence tells you which link failed: no DS found, no DNSKEY found, DS present but matching no key, or signatures invalid or expired. Use that to decide where to start fixing.
How do I confirm the fix on re-scan?
Check it yourself before re-scanning. Ask for the zone's SOA with DNSSEC data and look for the ad flag from a validating resolver:
dig +dnssec SOA example.com @1.1.1.1
The ad (authenticated data) flag in the response header means the resolver validated the answer. For a step-by-step chain walk, use delv, which ships with BIND:
delv @1.1.1.1 example.com SOA +rtrace
A successful run reports fully validated. A failure prints which step broke. You can also check the DS record directly:
dig +short DS example.com
When these agree, trigger a re-scan. The finding should clear once the chain validates end to end.
Common questions
Does DNSSEC encrypt DNS traffic?
No. DNSSEC signs answers so a validating resolver can detect tampering, but queries and responses still travel in clear text unless you add a transport such as DNS over TLS. It provides authenticity and integrity, not confidentiality.
What happens if the DS record and the zone's keys do not match?
Validating resolvers return SERVFAIL, so your domain becomes unreachable for users behind them. A DS record at the parent promises a signed zone. If DNSKEY is missing, signatures are expired, or the DS digest matches no key, validation fails. Remove the DS or repair the signing before anything else.
How long until the re-scan passes?
Once the DS is live at the parent and the zone signs correctly, the next scan should pass. Any delay comes from caching: parent TTLs on the DS record, often hours to a day, and your own record TTLs. Query the authoritative servers directly with dig to confirm sooner than the resolvers do.
Key takeaways
- A complete chain needs a DS record at the parent, a DNSKEY in the zone, and valid RRSIG records over the answers.
- A broken chain is worse than none, because validating resolvers refuse to answer.
- Sign the zone first, verify it, then publish the DS record at the registrar.
- Watch signature expiry and keep all authoritative servers consistent.
- SetEnforce checks the parent DS, the zone DNSKEY, and signature validity the way a validating resolver does, so you can confirm a fix with
delvordig +dnssecbefore you re-scan.