Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Domains & DNS

DNSSEC DS records: how the parent zone links to your DNS keys

Published August 2026 · 2 min read · Updated 2026-09-05

A DNSSEC DS record is the parent-zone pointer that lets a validating resolver trust a child zone key. Publishing a DS is not the same as enabling a DNSSEC switch; the values must be derived from the active key and remain coordinated through key or DNS-provider changes.

Know where the DS record belongs

The child DNS provider publishes DNSKEY records; the registrar or parent zone publishes the DS. Adding a DS-looking record inside the child zone does not create the parent chain of trust.

For .ca, .com, and other TLDs, the registrar interface and supported algorithms/digests can differ.

Match key tag, algorithm and digest

Copy the DS values exactly from a trusted DNS provider output or calculate them from the intended DNSKEY. A single wrong digest produces validation failure after the parent publishes it.

Check which DNSKEY is acting as the key-signing key when the provider exposes multiple keys.

Verify after parent publication

Query the parent delegation and a validating resolver after the DS becomes visible. Confirm the chain reaches the active DNSKEY and a signed record under the domain validates successfully.

Keep authoritative service stable while parent caches age.

Plan provider changes around DS removal/replacement

Changing nameservers while an old DS remains can make the new unsigned or differently signed zone unreachable to validating clients. Coordinate old/new signing state and parent DS before moving delegation.

  • DS lives at the parent.
  • Use values from the active key.
  • Validate the full chain after publication.
  • Coordinate DS during nameserver moves.

Next step

Understand DS records, key tags, digest algorithms and rollover timing so DNSSEC changes at the registrar match the keys actually signing the zone.

Explore DotMoose domains and DNS

Keep reading

Related guides.

CAA record planning: control which certificate authorities may issue for a domain

Plan CAA records around the certificate providers you use, subdomains and incident contacts, then verify issuance will still work before enforcing restrictions.

Read the guide

CNAME chain problems: why extra DNS aliases can break or slow resolution

Trace CNAME chains, loops, missing terminal records and provider restrictions, then shorten unnecessary aliases without changing the intended hostname.

Read the guide

DKIM selector rotation: change signing keys without breaking verification

Rotate DKIM selectors by publishing the new key first, switching signers, monitoring authentication and retaining the old selector long enough for queued mail.

Read the guide

More domains & dns guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move