Three laws behind every domain, shown before you pay · Swiss .ch held in Panama · Data out only on a Panamanian order · Paid in crypto
Language: English
Search a domain

Guide · checked 16 November 2026

How to enable DNSSEC on a domain?

DNSSEC needs two things done in the right order: the DNS host signs the zone, then the registrar puts a DS record in the parent zone. Done backwards, the domain stops resolving.

Last updated: · 6 min read

Quick answer

How to enable DNSSEC on a domain?

Have the DNS host sign the zone, then publish its DS record (key tag, algorithm, digest type, digest) at the registry through the registrar, and check the chain with a validating lookup. Fjordregis does both in one click on its own nameservers, and accepts up to 6 DS records from an outside DNS provider.

In brief
  • What it does: adds signatures to DNS answers so resolvers can check origin and integrity; it does not encrypt anything.
  • Chain of trust: the root zone has been signed since 2010; each parent holds a DS record pointing to the child's key (RFC 4034, section 5).
  • Two jobs: the nameserver operator signs; the registrar submits the DS record to the registry.
  • Order matters: before changing nameservers, turn DNSSEC off or replace the DS records, or resolution fails.
  • At Fjordregis: managed DNSSEC with its nameservers, or DS records pasted from another provider, at no extra cost.

Which DNSSEC setup fits which DNS host?

DNSSEC paths by DNS host, with who signs and who publishes the DS record, 16 November 2026
DNS hostWho signs the zoneWho publishes the DS record
Fjordregis nameserversFjordregis (Sign this zone with DNSSEC)Fjordregis, at the registry
CloudflareCloudflare (DNS › Settings › DNSSEC)Customer pastes the DS record in the DNSSEC tab
Own or host nameserversThe operator of the nameserversCustomer pastes the DS record in the DNSSEC tab
.ch with CDS supportThe operator of the nameserversSWITCH can read CDS records published by the operator
.is at ISNIC directlyThe operator of the nameserversHolder, under Edit DS records, then Commit changes

What are the steps to enable DNSSEC on a domain?

Labels in steps 3 to 5 are those of the DNSSEC tab in the Fjordregis client area.

  1. Check that the registry supports DNSSEC

    IANA's root zone page for the extension shows a DS record when the TLD is signed; .ch, .is, .de and .com all have one. If a registry does not support it, the DNSSEC tab says so.

  2. Decide who signs

    SWITCH puts it simply: the operator of the nameservers has to set DNSSEC up. That is the DNS host, which may differ from the registrar.

  3. Managed path: sign in one click

    With Fjordregis nameservers, open the domain's DNSSEC tab and choose “Sign this zone with DNSSEC”. The records are signed and the DS record is published at the registry; the status moves from Pending to Active, which can take a few hours.

  4. External path: copy the DS record

    At the outside provider, turn DNSSEC on and copy the DS record: key tag, algorithm, digest type and digest. Cloudflare shows it under DNS › Settings › DNSSEC.

  5. Paste and save the DS records

    In the DNSSEC tab, use Paste a DS record or Add a DS record, then click Save DS records. Up to 6 DS records are accepted; saving an empty list turns DNSSEC off.

  6. Verify the chain

    Query the DS record at the parent and a signed answer from a validating resolver; the RDAP record's secureDNS block should show the delegation as signed.

Verify DNSSEC from a terminal
# DS record published in the parent zone
dig +short DS example.com

# Signed answer: look for the ad flag and RRSIG records
dig +dnssec example.com A @1.1.1.1

# Same check through RDAP
curl -Ls https://rdap.org/domain/example.com | jq .secureDNS

What does DNSSEC protect against, and what not?

DNSSEC proves that a DNS answer comes from the zone it claims and was not changed on the way; it gives no confidentiality. ICANN describes the two features as data origin authentication and data integrity protection. When a signature fails, the validating resolver discards the data and returns an error, so a forged address never reaches the user.

The protection works only if every level is signed. ICANN notes the root zone has been signed since 2010, all generic extensions are signed and many country codes too. Each zone's key is vouched for by its parent through the DS record, which RFC 4034 defines in section 5 as a record that refers to the child's DNSKEY and appears only on the parent side of the delegation.

What is a DS record, field by field?

A DS record holds four fields: the key tag, the algorithm number, the digest type and the digest of the child zone's key. RFC 4034 defines them in sections 5.1.1 to 5.1.4. The key tag identifies which DNSKEY is meant; the algorithm matches that key's algorithm; the digest type names the hash; the digest is the hash itself.

Fjordregis checked the RDAP record of example.com on 16 November 2026: the delegation is signed, with algorithm 13 and digest type 2. IANA's page for .ch shows the same pair for the Swiss TLD itself. Those are the values most DNS hosts produce today, and they are what the Fjordregis DNSSEC tab expects in its Algorithm and Digest type fields. Reading secureDNS is covered in how to check a domain's RDAP record.

Which is the best way to enable DNSSEC in 2026: managed or manual?

Managed DNSSEC is the best choice when the registrar also hosts the DNS, because one party signs, rolls keys and publishes the DS record; manual DS entry is for zones hosted elsewhere. The managed option removes the most common failure, a DS record left at the registry after the keys changed.

The Fjordregis DNS offer reads: free DNS hosting with A, AAAA, CNAME, ALIAS, MX, TXT, NS, SRV and CAA records, managed DNSSEC, and your own nameservers if you prefer (2 to 13). The client area warns that managed DNSSEC works only with Fjordregis nameservers; with others, the customer publishes the DS records the DNS provider gives. Nameserver choices are explained in set nameservers and DNS, and DNS hosting is included in every price on the pricing page.

How do you change nameservers without breaking DNSSEC?

Turn DNSSEC off or replace the DS records first, wait for the change to spread, then move the nameservers. The Fjordregis Nameservers tab blocks the mistake with a warning: turn off DNSSEC or update your DS records first, or the domain stops resolving. ISNIC's FAQ gives the same advice for .is, with at least 24 hours between steps so resolvers see the new keys.

The same care applies to a registrar transfer that also changes DNS host, as in how to transfer a .ch domain. Keeping the current nameservers during the transfer avoids the problem entirely.

Frequently asked questions

Does DNSSEC cost extra at Fjordregis?

No. Managed DNSSEC is part of the free DNS hosting Fjordregis includes with every domain, and pasting DS records from another provider is free too.

How long does DNSSEC take to activate?

In the Fjordregis DNSSEC tab, the status shows Pending while the DS record is published at the registry, which can take a few hours, then Active.

Can I use DNSSEC with Cloudflare and Fjordregis?

Yes. Copy the DS record from Cloudflare's DNSSEC settings and paste it in the Fjordregis DNSSEC tab, then save.

Does DNSSEC encrypt DNS queries?

No. ICANN lists only origin authentication and integrity. Fjordregis recommends it against forged answers, not for privacy.

Is DNSSEC available on .ch?

Yes. SWITCH introduced DNSSEC in 2010 and its terms ask for a working copy of the public key. Fjordregis manages it on .ch with its nameservers.

Verdict
  • Use Fjordregis managed DNSSEC if the domain uses Fjordregis nameservers: one click, DS record published for you, no extra cost.
  • Paste the DS record by hand if the zone lives at Cloudflare or a host, and always clear it before moving nameservers.
Sources (6)
  1. DNSSEC: what is it and why is it important? — ICANN (read 2026-11-16)
  2. RFC 4034: Resource Records for the DNS Security Extensions (sections 2, 5) — IETF (read 2026-11-16)
  3. DNSSEC — SWITCH (read 2026-11-16)
  4. General Terms and Conditions for .ch and .li (clause 3.1.3) — SWITCH (read 2026-11-16)
  5. Frequently asked questions (DNSSEC, DS records) — ISNIC (read 2026-11-16)
  6. Root Zone Database: .ch (secure delegation) — IANA (read 2026-11-16)

DNSSEC in one click

Free DNS hosting with managed DNSSEC on every Fjordregis domain, paid in crypto.

.ch $42.49/year · .com $12.49/year · no KYC

Search a domain