The domain’s DNSSEC chain is broken, so every validating resolver — Cloudflare, Google, Quad9 — refuses to answer for it and the whole domain goes dark. The classic cause is a DS record left at the registrar after changing DNS host; the fix is to remove it or sign the zone to match.
; EDE: 9 (DNSKEY Missing): (No DNSKEY matches DS RRs of example.com)
How 4 other clients word the same error
Cloudflare 1.1.1.1
; EDE: 6 (DNSSEC Bogus): (proof of non-existence of example.com. A)
Expired signatures
; EDE: 7 (Signature Expired): (for DNSKEY example.com., id = 12345: RRSIG example.com., expiration = 123456)
Missing signatures
; EDE: 10 (RRSIGs Missing): (for DNSKEY example.com., id = 12345)
BIND logs
RRSIG has expired
| Error | EDE: 6 (DNSSEC Bogus) |
| Usually fixed by | The domain owner |
| Resolvers answer | SERVFAIL, with an extended error (EDE 6, 7, 9, 10 or 12) |
| Most common cause | A DS record at the registrar that matches no key in the zone |
| Fix takes effect | After the DS record’s TTL — set by the TLD, e.g. a day for .com |
Look up the domain’s DNS
We ask a validating resolver, so a broken chain shows up as “present, not validated” or a failure here.
What it means
With DNSSEC, the parent zone (the TLD) holds a DS record vouching for your zone’s key, and your zone signs its records with it. A validating resolver checks the whole chain; if a link does not match — a DS with no matching DNSKEY, a signature that has expired — the answer is “bogus”, and the resolver returns SERVFAIL rather than something it cannot trust.
That is by design, and it is why broken DNSSEC takes the whole domain down on 1.1.1.1 and 8.8.8.8 while resolvers that do not validate still work.
Why it happens
- The DNS host changed but the old DS record is still at the registrar — the new host signs with different keys, or not at all.
- DNSSEC switched off at the DNS host without removing the DS first.
- Signatures not refreshed in time, so they expired — or a server clock far enough out to make them look expired.
- A key or algorithm rollover done in the wrong order.
How to fix it
- Confirm it: dig the name through 1.1.1.1 — with +cd it works, without it SERVFAILs, and the EDE line names the reason.
- If you no longer use DNSSEC, remove the DS record at the registrar. If you do, enable DNSSEC at the current DNS host and replace the DS with the one it gives you.
- Wait out the DS record’s TTL — resolvers keep the old one until it expires — then check again.
- Next time, remove the DS before changing DNS host or switching DNSSEC off, and wait its TTL before the change.
See it for yourself
dig example.com A @1.1.1.1
dig example.com A @1.1.1.1 +cd
dig example.com DS +short
dig example.com DNSKEY +short
Works with +cd and fails without it means DNSSEC. Compare the DS the TLD publishes with the DNSKEY your zone serves: the key tag and algorithm must match.
Questions
Why does my domain work on some networks and not others?
Only validating resolvers reject a broken chain. Cloudflare, Google and Quad9 validate; some ISP resolvers do not, so the domain seems fine there.
Sources
Error text and meaning checked on 25 September 2026 against these official sources:
- RFC 4035 — rfc-editor.org
- RFC 8914 — rfc-editor.org
- Extended DNS error codes — developers.cloudflare.com
- Domain Troubleshooting — developers.google.com
- DNSSEC Guide — bind9.readthedocs.io