---
title: "DNSSEC"
description: "Sign a zone, add its DS at your registrar, check the chain, and turn DNSSEC off in the order that keeps your domain resolving."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.ezghcloud.com/llms.txt
> Use this file to discover all available pages before exploring further.

# DNSSEC

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

```sh
ezgh dns zones dnssec enable example.com
```

The 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](/dns-api/EnableZoneDnssec/), and the values appear in `dnssec.dsRecords` on
[GetZone](/dns-api/GetZone/).

## Add the DS at your registrar

Each DS value has four parts, which most registrars ask for separately:

```text
48213 13 2 3B7A1F0E9C5D4A2286E1B0C7D9F4A6E25C13D80F7B2946AE01C5D7E3F8A4B621
│     │  │ └ digest
│     │  └ digest type (2 is SHA-256)
│     └ algorithm (13 is ECDSA P-256)
└ key tag
```

Validation starts once your registrar publishes it. To check, ask a validating resolver and look
for the `ad` flag:

```sh
dig +dnssec A example.com @1.1.1.1
```

## Turn it off

For a zone that serves a domain registered in [EZGH Domains](/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](/domains/manage-a-domain#dnssec).

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:

1. **Note the DS's TTL** at the parent zone: `dig DS example.com`, while it's still there.
2. **Remove the DS** at your registrar.
3. **Wait** until `dig DS example.com` no longer shows it, then for that TTL to pass.
4. **Disable DNSSEC:**

   ```sh
   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](/dns-api/DisableZoneDnssec/). Turning DNSSEC on again later gives the zone
new DS values, which go through the same steps.

Source: https://docs.ezghcloud.com/dns/dnssec/index.mdx
