How to fix: DNSSEC DS Record Missing
No DS (Delegation Signer) record exists in the parent zone for this domain. DS records are required to establish the DNSSEC chain of trust from the parent zone to the child zone.
Why it matters
Without a DS record in the parent zone, DNSSEC validation fails or is bypassed entirely. Resolvers cannot build a chain of trust and may treat the zone as unsigned, allowing DNS cache poisoning attacks.
DNSSEC works by creating a chain of trust from the DNS root down to the domain. The DS record in the parent zone (e.g., the TLD) contains a hash of the child zone's DNSKEY, linking the two zones together. Without the DS record, even a fully signed child zone cannot be validated by resolvers.
How to fix it
- 1Generate DNSSEC keys for your zone using your DNS provider or BIND.
- 2Submit the DS record to your domain registrar to publish it in the parent TLD zone.
- 3Verify the chain: dig +dnssec DS example.com
Code examples
Check DS record
dig +short DS example.com @1.1.1.1Verify DNSSEC chain
dig +dnssec +multiline A example.com | grep -E '(RRSIG|NSEC|ad)'References
Detected automatically by VulnRadar. The check id is dns-ds-record-missing, stable across every scan so you can filter or diff on it.
More dns checks
Questions
- How severe is DNSSEC DS Record Missing?
- VulnRadar rates this medium severity in the dns category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id dns-ds-record-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.