DNSSEC signs a zone’s answers, so resolvers that validate can tell they’re genuine. It takes two sides: the zone is signed here, and a DS record at your registrar vouches for the signature.
Zones are signed with ECDSA P-256 (algorithm 13).
Turn it on
ezgh dns zones dnssec enable example.comThe command prints the zone’s DS values once signing starts. A pending zone starts signing when it
goes active, and ezgh dns zones get example.com shows them then. With the API, this is
EnableZoneDnssec, and the values appear in dnssec.dsRecords on
GetZone.
Add the DS at your registrar
Each DS value has four parts, which most registrars ask for separately:
48213 13 2 3B7A1F0E9C5D4A2286E1B0C7D9F4A6E25C13D80F7B2946AE01C5D7E3F8A4B621
│ │ │ └ digest
│ │ └ digest type (2 is SHA-256)
│ └ algorithm (13 is ECDSA P-256)
└ key tagValidation starts once your registrar publishes it. To check, ask a validating resolver and look
for the ad flag:
dig +dnssec A example.com @1.1.1.1Turn it off
For a zone that serves a domain registered in EZGH Domains, turn DNSSEC off from the domain instead: it removes the DS at the registry and waits before it stops signing. See Manage a domain.
Disabling stops signing at once. If the DS is still at your registrar when that happens, resolvers that validate get unsigned answers where they expect signed ones, and your domain stops resolving for them. Do it in this order:
-
Note the DS’s TTL at the parent zone:
dig DS example.com, while it’s still there. -
Remove the DS at your registrar.
-
Wait until
dig DS example.comno longer shows it, then for that TTL to pass. -
Disable DNSSEC:
ezgh dns zones dnssec disable example.com
The CLI asks before it disables, and --yes confirms in a script. With the API, this is
DisableZoneDnssec. Turning DNSSEC on again later gives the zone
new DS values, which go through the same steps.