Skip to main content

DNSSEC

DNSSEC helps protect your zones against forged or altered DNS responses. In DigiCert®​​ DNS, you can sign a primary zone, view its signing keys and records, and check its DS record configuration.

What DNSSEC is

Domain Name System Security Extensions (DNSSEC) use digital signatures to let validating DNS resolvers check that DNS data is authentic and has not been modified. DNSSEC does not encrypt DNS queries or responses.

The DNSSEC chain of trust connects your zone’s signing keys to a trusted starting point, normally the DNS root. The parent zone publishes a delegation signer (DS) record that identifies a DNSKEY in your zone.

For example, the DS record for example.com is published in the .com parent zone through your domain registrar. Publishing the matching DS record connects your signed zone to this chain of trust.

The DS record must match the appropriate DNSKEY. A mismatch can break validation and cause DNS resolution failures for users of validating resolvers.

Explore the DNSSEC page

To view DNSSEC settings for a primary zone, go to DNS > Zones, select Primary zones, open the zone, and select the DNSSEC tab.

Before the zone is signed, the page displays the Sign zone action and the Signing configuration:

Field

Description

Crypto algorithm

The algorithm used to generate DNSSEC signatures

RRSIG signature duration

How long generated signatures remain valid

KSK bit length

The size of the key signing key, in bits

KSK rollover period

The configured interval for replacing the key signing key

ZSK bit length

The size of the zone signing key, in bits

ZSK rollover period

The configured interval for replacing the zone signing key

Enable DNSSEC

To enable DNSSEC, sign the zone, then add the supplied DS record at your domain registrar. Before you begin, make sure you can manage the domain’s DS records at its registrar:

  1. Review the signing configuration and select Sign zone.

  2. Optionally, enter a Comment for the audit log.

  3. Select Sign.

  4. Use the information in Complete DNSSEC setup to add the DS record at your registrar.

  5. After the registrar publishes the change, return to the DNSSEC tab and check for setup messages.

Depending on your registrar, you may need to enter Key tag, Algorithm, Digest type, and Digest separately.

Notice

Signing the zone alone does not complete DNSSEC setup. The matching DS record must also be published in the parent zone.

After signing, the DNSSEC page displays the zone’s keys and associated records:

Information

Description

Key signing key (KSK)

The key’s status, ID, algorithm, size, effective period, creation date, and next rollover date

DS record

The information to publish through your domain registrar

KSK DNSKEY record

The public key used to verify signatures on the zone’s DNSKEY record set

Zone signing key (ZSK)

The key’s status, ID, algorithm, size, effective period, creation date, and next rollover date

ZSK DNSKEY record

The public key used to verify signatures on the zone’s other signed record sets

Select View raw data beside a DS or DNSKEY record to view and copy the complete record.

To check whether further action is needed, review any setup messages displayed on the page:

Message

Meaning

Action

Pending DNSSEC setup

The required DS record has not yet been verified in the parent zone

Add the supplied DS record at your registrar. If already added, allow time for publication and cached data to expire

DS record mismatch

The DS record does not match the zone’s DNSSEC configuration

Update the DS record at your registrar to match the information on the DNSSEC page

DS record lookup failed

The lookup could not verify the DS record

Try again. If the message persists, check the DS record with your registrar

A key’s Valid status describes that key. It does not, by itself, confirm that the parent-zone DS record is correct or that setup is complete.

Disable DNSSEC

To disable DNSSEC, first remove the domain’s DS records through your registrar, then unsign the zone in DigiCert®​​ DNS.

If a DS record remains available after the zone is unsigned, validating resolvers may reject the zone’s responses.

  1. Remove the domain’s DS records through your registrar.

  2. Verify their removal and allow time for cached DS records to expire.

  3. Open the zone’s DNSSEC tab.

  4. Select Unsign zone.

  5. Review the warning and optionally enter a Comment for the audit log.

  6. Select Unsign.

If you are unsure how to remove or verify DS records, contact your domain registrar.

DNSSEC keys and records

DNSSEC uses private keys to generate signatures and public keys to verify them. DigiCert®​​ DNS displays two signing-key roles:

Key

Purpose

Key signing key (KSK)

Signs the zone’s DNSKEY record set. Its corresponding DS record establishes trust through the parent zone

Zone signing key (ZSK)

Signs the zone’s other authoritative record sets, such as A and MX records

The DS record links the parent zone to a DNSKEY in your zone. Publish its values through your domain registrar:

Field

Description

Key tag

A numeric value that helps identify the corresponding DNSKEY

Algorithm

The numeric identifier of the DNSKEY’s cryptographic algorithm

Digest type

The numeric identifier of the hash algorithm used to create the digest

Digest

A hash derived from the DNSKEY and its owner name

The DNSKEY record publishes the public key that resolvers use to verify signatures:

Field

Description

Flag

Indicates key properties; typically 257 for a KSK and 256 for a ZSK

Protocol

Must be 3 for DNSSEC

Algorithm

The numeric identifier of the public-key algorithm

Public key

The encoded public-key data used for signature verification

An RRSIG record contains a digital signature covering a DNS record set. Its validity period is separate from the record’s caching TTL.

DNSSEC key rollover

Key rollover replaces a signing key while allowing validation to continue during the transition. The DNSSEC page displays each key’s Next rollover date and the configured rollover periods.

A KSK rollover generates a new signing key while keeping the current key active during the transition. It requires an updated DS record at your registrar:

  1. Review the Roll over KSK confirmation and select Roll over.

  2. Obtain the new DS record information.

  3. Add the new DS record at your registrar as soon as possible.

  4. Allow time for publication and cached DNS data to expire.

  5. Verify the new chain of trust before retiring the previous DS record.

Do not remove the previous DS record prematurely. Resolvers may still hold cached keys or records.

A ZSK rollover changes the key used to sign the zone’s other record sets. With separate KSK and ZSK roles, it normally does not require a registrar DS update because the KSK remains the link to the parent zone.

Notice

Failure to publish the new DS record during a KSK rollover can cause DNS resolution failures when the previous key is retired.