liveBook · Manning

Zone delegation

As explained in Effective Platform Engineering

Zone delegation is the DNS configuration that assigns authority for a domain or subdomain to the name servers of another hosted zone.

Zone delegation assigns authority for a domain or subdomain to the name servers of another hosted zone, allowing separate accounts to manage different environments. section 7.1.3

A practical platform arrangement:

  • Register the main domain in the production account and use its hosted zone for top-level traffic. section 7.1.3
  • Create hosted zones for environment subdomains such as dev.epetech.io, qa.epetech.io, and preview.epetech.io in the accounts that manage them. section 7.1.3
  • Publish NS records in the primary zone to delegate each subdomain to its separate hosted zone. section 7.1.3

Environment routing

A team can receive dev, QA, and production environments by mapping dev.epetech.io and qa.epetech.io to nonproduction resources while retaining epetech.io for production UI traffic. section 7.1.3

How Effective Platform Engineering covers it

How deep it goes
Shows account-level hosted zones, cross-account providers, and Terraform patterns for creating subdomains and delegations.
Examples
Uses epetech.io with dev, QA, production, preview, API, and sandbox subdomains across two AWS accounts.
What it assumes
Assumes familiarity with domains, AWS accounts, hosted zones, and subdomains while making account-level delegation concrete.
What you can do after
Operate/configure delegated DNS with Route 53 and Terraform across production and nonproduction AWS accounts.
How it connects
Connects DNS, hosted zones, Route 53, Terraform, subdomains, AWS accounts, and Kubernetes namespaces.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Effective Platform Engineering. The section links point to the parts of the book it draws on.