Name servers & SOA · Lesson 6 of 8 · 3 min read
Operating authoritative DNS
Migrating a zone from BIND (or another provider) to Route 53
- Export the existing zone (zone file or provider export). Inventory MX, TXT (SPF/DKIM/DMARC/verification), CAA, SRV, delegations, wildcard records.
- Import into a new Route 53 hosted zone (
aws route53 change-resource-record-setsbatches, Terraform, or the console's zone file import). - Verify by querying the new name servers directly and diffing against the old (
dig @ns-xxx.awsdns-xx.com name type) for every record. - Lower TTLs on the old provider (records and NS) well ahead.
- Switch NS at the registrar to Route 53's four servers.
- Keep the old provider serving identical data for at least 48 hours (parent NS TTL).
- Monitor resolution from multiple networks; then decommission the old zone and raise TTLs.
After a registrar transfer (moving the domain itself to another registrar), the first check if resolution breaks: the NS records at the new registrar still point to your DNS provider.
Enlarge diagram
Swipe sideways to see all of it, or tap to open it full screen.
DNS as code
Manage records in Git — Terraform (aws_route53_zone, aws_route53_record), octoDNS, or External DNS from Kubernetes — with PR reviews, plan output and drift detection. Benefits: audit trail, easy rollback, consistent multi-provider data, no "who changed MX at 3 PM?".
Resilience and monitoring
- Name servers on different networks/providers so DNS survives the loss of one.
- Monitor resolution of critical names from multiple locations (synthetic checks), SERVFAIL/NXDOMAIN rates, answer correctness, query latency, and record drift versus code.
- Alert on changes to NS/SOA and on registrar-level changes (domain expiry! auto-renew on, registrar lock enabled, contact details current).
- Protect against hijacking: registrar account MFA, registry/registrar lock, DNSSEC.