Enable DNSSEC safely (and fix a broken setup)
Sign your DNS so answers can't be forged — and avoid the stale DS record that takes domains offline.

DNSSEC adds digital signatures to your DNS so resolvers can detect forged answers. It needs two parts: signing at your DNS host and a DS record at the registry.
Turn it on
- Sign the zone. In cPanel open Domains → Zone Editor and click DNSSEC next to the domain (if your plan shows it), then Create Key with the default algorithm 13 (ECDSA P-256). With another DNS provider, use its DNSSEC switch.
- Copy the DS record it shows (key tag, algorithm, digest type and digest).
- Add the DS record at your registrar. For domains registered with Enet, open the domain in the client area and use DNSSEC Management, or open a ticket and paste the DS details. This works for .ke domains and most gTLDs.
- Wait an hour, then confirm with the DNSSEC checker — it should say DNSSEC is working.
"Bogus" — the dangerous case
If the registry has a DS record but your zone's keys don't match (common after moving DNS to a new provider), validating resolvers refuse to answer. For many visitors the domain simply disappears.
Fix it immediately:
- Remove the old DS record at the registrar, or replace it with the DS from the new DNS host.
- Wait for the registry's DS TTL to pass (often an hour, up to a day).
Signed but not linked
If your zone has keys but the registry has no DS record, nothing breaks — but nothing is protected either. Add the DS record as in step 3.
Was this article helpful?
Your vote helps us write better guides.
