Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Domains & DNS

DNSSEC validation errors: trace broken signatures and delegation

Published August 2026 · 2 min read · Updated 2026-09-05

DNSSEC validation errors occur when the chain of trust says signed data should verify but a resolver cannot validate it. The resulting failure can look like a domain outage even though authoritative servers still answer. Troubleshooting should follow the chain from parent DS to child DNSKEY and signed RRsets.

Confirm the failure with a validating resolver

Compare a validating public resolver with direct authoritative queries. If authoritative servers answer but validating recursive resolvers return SERVFAIL, DNSSEC becomes a strong suspect.

Use DNSSEC-aware tools that display DS, DNSKEY, RRSIG, algorithm, key tag and validation state.

Check parent DS against active DNSKEY

The DS record lives at the parent and must correspond to a DNSKEY published by the child zone. A stale DS after changing DNS providers is a common way to create a signed-but-unverifiable delegation.

Verify the key tag, digest type, digest and algorithm together.

Inspect signatures and time validity

RRSIG records have inception and expiration times. Clock errors or a signing system that stopped refreshing signatures can invalidate otherwise correct keys.

Confirm all authoritative servers serve the same current signed zone and that denial-of-existence records such as NSEC/NSEC3 are coherent.

Recover without creating a longer broken chain

Fix the signing/key mismatch at the correct layer. If DNSSEC must be removed, follow the registrar or DNS-provider procedure so the parent DS is removed safely before signing is disabled in the child.

  • Compare validating and authoritative answers.
  • Match parent DS to child DNSKEY.
  • Check signature timing.
  • Remove DNSSEC only with chain-aware sequencing.

Next step

Diagnose SERVFAIL and DNSSEC validation failures by checking signatures, keys, DS records, time, delegation and the chain of trust from parent to zone.

Explore DotMoose domains and DNS

Keep reading

Related guides.

CAA record planning: control which certificate authorities may issue for a domain

Plan CAA records around the certificate providers you use, subdomains and incident contacts, then verify issuance will still work before enforcing restrictions.

Read the guide

CNAME chain problems: why extra DNS aliases can break or slow resolution

Trace CNAME chains, loops, missing terminal records and provider restrictions, then shorten unnecessary aliases without changing the intended hostname.

Read the guide

DKIM selector rotation: change signing keys without breaking verification

Rotate DKIM selectors by publishing the new key first, switching signers, monitoring authentication and retaining the old selector long enough for queued mail.

Read the guide

More domains & dns guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move