What is domain delegation?

Domain delegation is the public instruction that tells the DNS system which name servers are authoritative for a domain.

Name serversDNS control planeDelegation signal

Direct answer

Domain delegation is the link between a registered domain and the authoritative name servers that publish its DNS records.

Plain-language explanation

When a domain is registered, the wider DNS system needs to know which name servers are allowed to answer for it. That instruction is called delegation.

The delegated name servers are where public DNS records for the domain are expected to be found. They help answer questions such as where the website points, where mail should go, and which public TXT records are published.

Changing delegation is different from changing one website record. It can move the visible DNS control plane for the domain from one provider, account or management path to another.

Why it matters

Delegation matters because it sits close to domain control. If the authoritative name servers change, the place that publishes the domain's public DNS answers may have changed.

That can be routine and expected. It may reflect a DNS provider migration, registrar-bundled DNS, agency handover, consolidation, platform change or administrative cleanup. It is still a meaningful public signal because many other records depend on the delegated name servers.

What .auDO observes

  • visible nameserver values for observed domains
  • inferred DNS provider context from nameserver patterns
  • changes in nameserver values between repeated observations
  • DNSSEC-related delegation evidence where visible
  • registration and registrar context that may sit alongside delegation changes
  • aggregate DNS provider patterns across the observed panel

What it can tell us

  • which name servers appeared authoritative at collection time
  • whether the visible DNS control-plane position changed
  • whether provider movement appears isolated or repeated
  • whether delegation should be reviewed alongside DNSSEC, registrar and mail posture
  • whether important domains appear to depend on concentrated provider families

What it cannot prove

  • why delegation changed
  • whether the change was authorised or expected
  • whether the new DNS hosting arrangement is better or worse
  • whether all records moved correctly
  • whether private DNS management processes are mature
  • whether an organisation's internal ownership model is clear

Practical governance questions

  • Who is allowed to change delegated name servers for important domains?
  • Are delegated providers documented separately from registrar and hosting providers?
  • Are delegation changes reviewed alongside mail, DNSSEC and website records?
  • Is there a clear rollback or review process when delegated name servers move?
  • Can non-technical domain owners understand the consequence of delegation changes?

These signal pages explain the public fields most relevant to delegation and DNS control-plane movement.

State pages summarise aggregate posture across the current .auDO observation panel. They are summaries, not scores.

Explore observed context

For broader context, compare delegation signals with dated reports, observed cohorts and related explainers.