How to enable / disable DNSSEC

Enable DNSSEC

You can quickly and easily enable DNSSEC on your domains installed on our NS, directly on your customer portal Domains > DNSSEC › Enable DNSSEC in the toolbar:

  1. Log in to your account
  2. Access your domain portfolio: go to the "Domains > Portfolio" menu item
  3. Select the domain(s) for which you want to enable DNSSEC
  4. In the bottom bar, click on DNSSEC and then on "⊕ Enable DNSSEC"
  5. Finished! Please wait 24-48 hours for DNSSEC to be activated.

 

 

You can also request activation in bulk — for multiple domains at once — though this will only work for domains that support it.

  1. Log in to your account.
  2. Access your domain portfolio: go to "Domains > Portfolio"
  3. Select the domain(s) for which you wish to enable DNSSEC
  4. In the bottom bar, click on "DNSSEC," then select "⊕ Enable DNSSEC"
  5. You're all set! Please allow 24–48 hours for DNSSEC to be activated.

 

Domains > Portfolio > Select domain > DNSSEC

 

 
Timing

  Step

   What happens

  Typical duration

1

Zone signing is requested at the DNS platform. A key entry appears in the key list, initially without public key data.

Immediate

2

The DNS platform generates the key and signs the zone. The key's public data appears in the list.

Usually within an hour or two

3

The next automation run submits the key to the registry. The key shows Delegated = yes from this point on.

Up to 6 hours after step 2

4

The registry publishes the DS record in the TLD zone.

Depends on the registry; varies greatly from TLD to TLD

 

Overall: BrandShelter submits the key to the registry within a few hours. How long the registry then takes to publish the DS record varies greatly from TLD to TLD.

The current signing algorithm is ECDSA P-256 with SHA-256 (algorithm 13). The registry derives the DS record from the submitted key.

 

 

Using external name servers

If you want to enable DNSSEC for a domain name registered with us but technically managed by an external DNS provider, you can follow the procedure above — setting up a DNS zone on our name servers if necessary (this will have no impact).

DNSSEC public keys (or DNSKEYs) can be added or modified directly using the BrandShelter portal.

You can add or update your DNSKEY via the DNS management interface for your domain, accessible through our platform > Domains > Select your domain > DNS > DNSSEC.

Note: An inactive zone must be created in order to access the DNSSEC option.
 

Once you have completed the necessary steps with your DNS provider to request DNSSEC activation and have obtained the DNSKEY information, navigate to the DNSSEC management page for your domain within our portal (DNS > DNSSEC).

Click "Add DNSKEY" and fill out the form to input the key that you previously generated and retrieved from your DNS provider for this domain.

 

Publishing your key

  1. Enable signing at your DNS operator and obtain the KSK (key-signing key, flags 257) as a full DNSKEY record: algorithm and public key. A DS record is not enough (see below).

  2. In BrandShelter, open the domain's DNSSEC page (Domains > DNS > DNSSEC) and click Add DNSKEY in the toolbar.

  3. Enter the algorithm and public key. Optionally set:

    • Valid from: the date from which the key should be published,

    • Expiration date or Validity: when the key should be removed,

    • Overlap: how long before expiry a successor key may be published alongside it.

  4. The next automation run submits the key to the registry. The registry then publishes the DS record. The timings are the same as detailed above, steps 3 to 4.

Make sure the zone is already signed with this key at your DNS operator before you add it. BrandShelter publishes enabled, valid keys at the next run.

Supported key algorithms are 5, 7, 8, 10, 13 and 14 (RSA/SHA-1, RSASHA1-NSEC3-SHA1, RSA/SHA-256, RSA/SHA-512, ECDSA P-256 and ECDSA P-384).

BrandShelter needs the full public key (DNSKEY), not just a DS record. TLDs differ in what they accept. Some registries require the full key, others accept only the DS hash, and they ask for different hash algorithms. With the full key, BrandShelter can provide whatever form each registry requires, so DNSSEC works for every TLD that supports it. If your DNS operator only shows you a DS record, ask them for the DNSKEY. Most operators display it next to the DS record. You can also retrieve it from the signed zone with dig +short DNSKEY example.com; use the entry starting with 257.

 

Rolling over your key

  1. Have your DNS operator publish the new key in the zone alongside the old one.

  2. Add the new key in BrandShelter with Add DNSKEY, and wait until it shows Delegated = yes and its DS record is visible in public DNS (see section: Verifying the result).

  3. In BrandShelter, disable the old key, or let it expire through the validity dates you set. The automation removes its DS record at the registry.

  4. Once the old DS record is gone from public DNS and its TTL has passed, remove the old key at your DNS operator.

 

Example of DNSSEC public key (or DNSKEY) - (Key format): 

DNSKEY 256 3 5 AQPSKmynfzW4kyBv015MUG2DeIQ3Cbl+BBZH4b/0PY1kxkmvHjcZc8noaNvv4w==
DNSKEY <flags> <protocol> <algorithm> <pubkey>


Retrieve the algorithm used to generate the public key from your DNS provider (for example, SHA-256) as well as the public key itself (the final part of the record — in the example above, this would be  AQPSKmynfzW4kyBv015MUG2DeIQ3Cbl+BBZH4b/0PY1kxkmvHjcZc8noaNvv4w== ), enter these into the form, and click "Create DNS key."

The other fields are optional.
 

 

 

Alternatively, if you encounter any difficulties, you can contact our Customer Care Service at support@brandshelter.com, or reach out to your account manager if you have one.

After completing the necessary steps with your DNS management provider to request DNSSEC activation and retrieve the DNSKEY information, please provide us with the required data as follows:
 

→ DS record:

DS 8997 13 2 e8lkcjRZvJorYc5NpRbv10xzxHZ6G0v2Vwg+5sfLlOfWk4WoFlO1A==

→ DNSKEY record (DNSSEC public key) : 

DNSKEY 256 3 5 AQPSKmynfzW4kyBv015MUG2DeIQ3Cbl+BBZH4b/0PY1kxkmvHjcZc8noaNvv4w==


→ and/or

Key tag: 
Algorithm:
Flags: 
Digest algorithm: 
Digest algorithm type: 
Digest: 
Signing algorithm: 
Signing algorithm type: 
Public key: 
DS record:

 

Important note:

• In the event of DNSSEC key changes or renewals (key rollovers), you must submit an update request to us; any modification to DNSKEYs requires an explicit request if external name servers are used.

• If the DNSKEYs have an expiration date and external name servers are used, you must periodically provide us with the updated information regarding the DNSKEYs and/or DS records.

• We recommend monitoring the validity of DNSKEYs and paying close attention to key renewals.

• Management must be handled on a domain-by-domain basis; no bulk update functionality is available. Furthermore, changes are not applied instantly and require propagation time.

 

 

Disable DNSSEC

To disable DNSSEC, follow the same steps and procedure.

  • Individual & Bulk management: In the domain portfolio, select the domain(s) and choose DNSSEC › Disable delegation signing in the toolbar at the bottom.
     

  • DNS panel: In the bottom bar, click on DNSSEC and then on Disable delegation signing.

Important: The option "🗑️ Disable DNSSEC" is only for domains without delegation signing (no DS records published).

 

DNSSEC always has to be switched off in this order:

  1. First remove the note at the registry (the DS record).
  2. Only then stop stamping the answers (zone signing).

→ Disable delegation signing starts this safe sequence. BrandShelter asks the registry to remove the DS record. Once the record has disappeared from public DNS, BrandShelter also stops zone signing automatically. You don't need to do anything else; the result is a fully disabled DNSSEC.

→ Disable DNSSEC stops zone signing immediately. That is only safe if there is no DS record at the registry, for example when DNSSEC was just enabled and the DS record hasn't been submitted yet. If a DS record is still published, BrandShelter refuses the action, because it would take the domain offline.


If you get the message: "Unable to disable DNSSEC on these domains:" then, the DNSSEC is probably already disabled for your domain(s).

You can check DNSSEC activation here:  https://dnssec-analyzer.verisignlabs.com/  or here: https://zonemaster.net/en/

 

 

In Brief

Action

Effect

Enable DNSSEC

Starts zone signing; the DS record is then published automatically

Disable delegation signing

Requests removal of the DS record. Zone signing is then removed automatically

Disable DNSSEC

Stops zone signing (no DS). This only applies to domains without delegation signing

 

Important:

  1. DNSSEC activation/deactivation for BrandShelter domains typically requires 24 hours (to 48 hours) between zone signing and the modification of the domain.
    For specific TLDs, activation times vary:
    .CH / .LI: Changes are activated after 3 days.
    .SK: Parent updates take 72 hours.
    .CZ: Parent updates take 7 days.
     
  2. We always recommend to wait at least 48 hours after disabling DNSSEC before enabling it again. Some DNS caches may still have old DNS keys cached even if their TTL has already expired.
    Standard practice for migrations/transfers involves deactivating DNSSEC and waiting 24 to 48 hours to allow DNS caches to catch up before reactivation.
     
  3. DNSSEC is not supported and cannot be activated on all extensions / TLDs, some registries / TLDs are not compatible.
    BrandShelter - List of TLDs supporting DNSSEC
    ICANN - List of TLDs supporting DNSSEC
     
  4. Certain types of DNS records are not supported for DNSSEC-signed zones. For example, the use of APEX ALIAS records is not supported for DNSSEC-signed zones, and in the worst-case scenario, this will compromise the DNSSEC security of the zone.
     
  5. Is there any risk associated with using DNSSEC with external name servers (NS), and if so, what is the level of risk? As long as DNS zones remain hosted on your own DNS infrastructure and the published DNSSEC information exactly matches the zone configuration, the risk level can be considered low. However, it is important to note that DNSSEC introduces an additional layer of operational complexity. Configuration errors, inadequate key rollover management, or inconsistencies between information published at the registry level and data on the DNS servers can lead to DNS resolution issues. This is a genuine risk to consider for DNSSEC-secured domains hosted on external name servers.
     
  6. Is maintenance required after activation for domains using external name servers? Yes. The main area requiring attention is DNSSEC key management and potential key rollover operations. Whenever DNSKEYs are renewed or replaced, the associated information must be updated to maintain the DNSSEC chain of trust. It is therefore recommended to regularly monitor key validity.
     
  7. Do DNSKEY updates need to be requested from or communicated to BrandShelter? This depends on the DNS infrastructure being used. When DNS zones are hosted on BrandShelter's DNS infrastructure, DNSSEC management is automated, and no action is required on your part for routine operations. When DNS zones are hosted on external DNS servers, manual maintenance is required; any changes to DNSKEYs must be accounted for and communicated to our team to maintain the DNSSEC chain of trust. In this latter scenario—using external name servers—no automated update mechanism is available.
     
  8. DNSSEC introduces an additional layer of operational complexity. The primary challenge generally lies not in the initial activation, but rather in the ongoing management of the DNSSEC key lifecycle, including key rollovers and updates to associated DNSSEC information. Mismanagement of these operations can lead to DNS resolution issues and even render a domain inaccessible to resolving servers that perform DNSSEC validation; this is a genuine risk that must be considered. Monitoring the validity of DNSKEYs and proactively managing key rollover operations are key operational priorities when DNS zones are hosted on external DNS infrastructure. While these considerations certainly do not diminish the security benefits of DNSSEC, they must be factored into any assessment of the cost-benefit ratio and the long-term operational processes associated with DNSSEC.
     
  9. DNSSEC has two parts that always have to match: 

    • Zone signing: the DNS provider signs all records of the domain, like a stamp of authenticity on every DNS answer.
    • Delegation signing (the DS record): the registry of the TLD publishes a note saying "answers for this domain are always stamped, and this is the stamp to expect".

    Resolvers that check DNSSEC, which includes most large providers such as Google, Cloudflare and many ISPs, read the registry's note first. If the note says "expect a stamp" but the answers arrive without one, they don't treat the answers as unsigned. They treat them as forged and refuse them. For a large part of the Internet the domain then simply stops working: no website, no e-mail.

 

 

Verifying the result

You can check the current state yourself with dig. Replace example.com with your domain.

# DS records published by the registry (delegation signing)
dig +short DS example.com

# Keys served by the zone (zone signing)
dig +short DNSKEY example.com

# Does the domain validate? Look for the "ad" flag; SERVFAIL indicates a DNSSEC problem
dig +dnssec example.com A @1.1.1.1

To see whether the TLD servers already publish the change, without any caching, query a TLD nameserver directly:

dig +short NS com.
dig +norec DS example.com @<one of the TLD nameservers>

Online tools such as DNSViz and the Verisign DNSSEC Debugger show the full chain of trust.


What the key list on the DNSSEC page shows:

  Column

  Meaning

Enabled

BrandShelter should keep this key published at the registry. No means removal has been requested.

Delegated

A matching DS record is visible in public DNS, or the key was submitted to the registry within the last 3 days.

Valid from / Expiration date

The publication window of the key.

 

The usual in-between states are:

  • Enabled = yes, Delegated = no: waiting for submission or for the registry.

  • Enabled = no, Delegated = yes: removal requested, and the DS record is still published.

 

 

The types of records used for DNSSEC

The Domain Name System Security Extensions (DNSSEC) protocol secures a DNS zone by signing records with a series of zone signing keys and key signing keys, and by providing final resolvers with a mechanism to authenticate and verify the integrity of DNS responses to queries. DNSSEC thus protects against attacks by digitally signing data to help ensure its validity. To ensure the security of a lookup, signing must occur at each stage of the DNS lookup process. The following DNS records are part of DNSSEC and are used for it.

  • DNSKEY record (DNSSEC public key): Contains a public key used by resolvers to verify DNSSEC (Domain Name System Security Extension) signatures in RRSIG records.

    DNSSEC uses public key cryptography to sign and authenticate DNS resource record sets (RRsets). The public keys are stored in DNSKEY resource records and are used in the DNSSEC authentication process described in [RFC4035]: A zone signs its authoritative RRsets by using a private key and stores the corresponding public key in a DNSKEY RR. A resolver can then use the public key to validate signatures covering the RRsets in the zone, and thus to authenticate them. The DNSKEY is not intended as a record for storing arbitrary public keys and MUST NOT be used to store certificates or public keys that do not directly relate to the DNS infrastructure.

    The DNSKEY has no special TTL requirements.

    More information on DNSKEY record


Format of a DNSSEC public key (DNSKEY)

DNSKEY 256 3 5 AQPSKmynfzW4kyBv015MUG2DeIQ3Cbl+BBZH4b/0PY1kxkmvHjcZc8noaNvv4w==
DNSKEY <flags> <protocol> <algorithm> <pubkey>

Parameters or KeyData : 

    DNSSEC# = <flags> <protocol> <algorithm> <pubkey>    

    Flags: 256, 257

    Protocol: 3 (DNSSEC)

    Algorithm: 2, 3, 4, 5, 6, 7, 8, 10, 12, 13, 14, 15, 16  > https://www.iana.org/assignments/dns-sec-alg-numbers

    Pubkey: <Holds the public key>
 

  • DS record (Delegation Signer): used by DNSSEC to enable the transfer of trust from a parent zone to a child zone. The DS record contains a cryptographic hash of a DNSKEY record.

    The DS Resource Record refers to a DNSKEY RR and is used in the DNS DNSKEY authentication process. A DS RR refers to a DNSKEY RR by storing the key tag, algorithm number, and a digest of the DNSKEY RR. Note that while the digest should be sufficient to identify the public key, storing the key tag and key algorithm helps make the identification process more efficient. By authenticating the DS record, a resolver can authenticate the DNSKEY RR to which the DS record points. The key authentication process is described in [RFC4035].

    The DS RR and its corresponding DNSKEY RR have the same owner name, but they are stored in different locations. The DS RR appears only on the upper (parental) side of a delegation, and is authoritative data in the parent zone. For example, the DS RR for "example.com" is stored in the "com" zone (the parent zone) rather than in the "example.com" zone (the child zone). The corresponding DNSKEY RR is stored in the "example.com" zone (the child zone). This simplifies DNS zone management and zone signing but introduces special response   processing requirements for the DS RR; these are described in [RFC4035]. The DS RR has no special TTL requirements.

    More information on DS Resource Record.
     

Format of a DS record

DS 8997 13 2 e8lkcjRZvJorYc5NpRbv10xzxHZ6G0v2Vwg+5sfLlOfWk4WoFlO1A==
DS <keytag> <algorithm> <digestType> <digest>

Parameters or DSData : 

    DNSSECDSDATA# = <keytag> <algorithm> <digestType> <digest>

    KeyTag: 0 - 65535

    Algorithm: 2, 3, 4, 5, 6, 7, 8, 10, 12, 13, 14, 15, 16  > https://www.iana.org/assignments/dns-sec-alg-numbers

    DigestType: 1 (SHA-1), 2 (SHA-256), 3 (GOST R 34.11-94), 4 (SHA-384)

    Digest: <Holds the digest>


Domain Name System Security (DNSSEC) Algorithm Numbers: https://www.iana.org/assignments/dns-sec-alg-numbers
 

  • NSEC and NSEC3 record (Next Secure/Next Secure v.3): It is used to prove that a requested DNS resource does not exist.
     
  • RRSIG record (RRset Signature - Resource Record Signature): contains a DNSSEC signature for a set of records (one or more DNS records with the same name and type). It stores the digital signatures used to authenticate records according to DNSSEC.

 

 

Glossary

 

Term

Meaning

DNSKEY

Public key published in the domain's zone.

KSK

Key-signing key (DNSKEY with flags 257); this is the key the DS record refers to.

DS

Delegation Signer record: a hash of the KSK, published by the registry in the TLD zone.

Delegation signing

BrandShelter's term for the DS record at the registry.

TTL

Time-to-live: how long resolvers may cache a record.

Validating resolver

A DNS resolver that checks DNSSEC signatures (e.g. 1.1.1.1, 8.8.8.8, most ISP resolvers).