Understand what a DNSSEC test says about your domain
A complete DNSSEC test asks two things: whether your DNS provider signs your records, and whether the DS record at your registrar matches those keys. If the two stop matching, resolvers that check signatures can fail to resolve your domain at all.
What is DNSSEC protecting?
DNSSEC authenticates DNS data so a validating resolver can detect answers that fail signature checks. It doesn't encrypt DNS queries. RFC 4033 explains those limits.
Enable DNSSEC with the DS record at your registrar
- 1
Start signing at the DNS provider
Confirm the DNS host and registrar support the setup, then enable signing and get the DS values the DNS provider supplies.
- 2
Publish the matching DS record
Add those values through the registrar, then test the whole chain with a tool such as DNSViz.
Plan DNSSEC before moving to another DNS provider
An old DS record can make validating resolvers reject the new provider's answers. Follow both providers' migration procedure before changing nameservers. If they support a signed migration, use that process; otherwise, follow their sequence for removing the old DS record and waiting for its cached copies to expire. Cloudflare documents both migration paths.
Frequently asked questions
Should I enable DNSSEC on my domain?
It's worth it if your DNS provider and registrar both support it and you'll keep the DS record in step when you change providers. Resolvers that check signatures can then reject spoofed answers for your domain.
Review certificate permissions and domain renewal after DNSSEC
Domain health
Fix the setup mistakes that make browsers warn people away from your site.
CAA record
Limit certificate issuance to the authorities your hosting setup needs.
Subdomain takeover
Clean up DNS names that still point to a service you no longer control.
Domain expiration
Review the registration date and renewal settings before your domain runs out.