What it means
The DS record at your registry matches a key your nameservers serve, but that key doesn't sign the zone's set of keys. The chain of trust needs the key named by the DS record to sign the DNSKEY records.
Why it matters
Resolvers can't follow the chain from the registry into your zone, so validation fails and the domain looks offline to most visitors. This usually happens in the middle of a key rollover, when a new key is published but the old DS record still points at a key that has stopped signing.
How to fix it
- Check your DNS provider's DNSSEC settings for the current key-signing key and its DS record.
- Publish that DS record at your registrar.
- Remove the DS record for the key that no longer signs, once the new one is live.
- If you sign the zone yourself, check that your signer still signs the DNSKEY set with the key in the DS record.
Check it worked
Run the DNSSEC and nameserver check again. The key table should show the matching key with a valid signature over DNSKEY.