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

Subdomain delegation: hand part of a DNS namespace to another set of nameservers

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

Subdomain delegation lets a parent zone give authority for a child such as app.example.com to a different nameserver set. It is useful when teams or platforms need independent control, but delegation introduces a second DNS authority and a clear boundary where records must live on one side or the other.

Choose the exact delegation boundary

Decide whether the child is a single hostname or an entire subtree. Delegating app.example.com means the child authority owns records at and below that name; ordinary records for the delegated node should not be split ambiguously between parent and child.

Keep unrelated parent-zone records untouched.

Create the child zone before parent NS records

Configure the child authority with SOA, NS, and required application records, then query those servers directly. Only after the child answers correctly should you publish NS delegation in the parent.

If child nameservers are inside the delegated zone, glue/address considerations may apply.

Plan DNSSEC across the delegation

A signed parent can securely delegate to a signed child using a DS for the child. If the child is unsigned, the parent must represent an insecure delegation correctly and must not publish a fabricated DS.

Coordinate key changes with whoever operates the child.

Monitor both authorities

Troubleshooting now requires checking parent delegation and child data. Document ownership and renewal/access for both DNS providers so one team cannot silently abandon the child zone.

  • Define the subtree owner.
  • Prebuild child authority.
  • Publish parent NS delegation.
  • Document DNSSEC/operational ownership.

Next step

Delegate a subdomain with NS records, verify the child zone and glue needs, and avoid conflicting records at the parent that make resolution ambiguous.

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