What is DNSSEC
DNSSEC (DNS Security Extensions, RFC 4033) adds cryptographic signatures to DNS records. A validating resolver checks the signatures from the DNS root down to the domain and rejects answers that do not match.
The chain of trust runs through the DS record in the parent zone: the registry publishes a fingerprint of the domain's key, and the domain signs its own records with that key.
Why it matters
Without DNSSEC, a forged DNS answer can send mail or visitors to the wrong server. With it, validating resolvers notice the forgery and refuse the answer.
DNSSEC is also the base for DANE, which publishes the TLS certificates of mail servers in DNS.
What a correct record looks like
Enable DNSSEC at your DNS provider, which signs the zone, and publish the DS record it gives you at your registrar.
DNS record
example.com. DS 2371 13 2 1F987CC6583E92DF0890718C42A3E0A6B6E9F1E8C2D0B1A4C7E5F3D2A1B0C9E8
Most DNS providers sign the zone with one setting. The DS record must match the current key, so a key change at the provider needs a matching DS update at the registrar.
Common problems
- DS record does not match
- When the DS record at the registrar points to a key the zone no longer uses, validating resolvers cannot resolve the domain at all. Update or remove the DS record.
- Expired signatures
- Signatures have an expiry time. A zone that is no longer re-signed fails validation when they expire.
- Moving DNS providers
- Moving a signed zone to a new provider without updating the DS record breaks the domain. Remove the DS record first, or move the keys with the zone.
- Not enabled
- An unsigned domain still works, but its DNS answers can be forged.