Route 53 at a glance
A Route 53 hosted zone is a container of DNS records for a domain. Public hosted zones answer the internet; private hosted zones answer only the VPCs you associate with them. Around them sits the Route 53 Resolver — the DNS server in every VPC — plus inbound/outbound endpoints for hybrid DNS with on-prem networks, DNS Firewall, query logging and Profiles for sharing configuration across accounts. Senior interviews test whether you can design DNS for a multi-account AWS organisation with EKS and on-prem connectivity, and debug "this name doesn't resolve from here".
What Route 53 does
| Capability | What it is |
|---|---|
| Domain registration | Register/transfer domains; auto-creates a public hosted zone |
| Hosted zones | Authoritative DNS — public and private |
| Routing policies | Simple, weighted, latency, failover, geolocation, geoproximity, multivalue, IP-based |
| Health checks | Monitor endpoints, other checks, or CloudWatch alarms; drive failover |
| Route 53 Resolver | The recursive resolver in every VPC, with endpoints and rules for hybrid DNS |
| Resolver DNS Firewall | Allow/block DNS queries from VPCs by domain lists |
| Query logging | Public zone query logs and VPC resolver query logs |
| Profiles | Share DNS configuration (private zones, rules, firewall) across VPCs/accounts |
| Application Recovery Controller | Controlled regional failover |
The name comes from DNS's port 53. Route 53 is a global service with a 100% availability SLA for DNS query answering.
Pricing basics
- Monthly fee per hosted zone (first 25 zones at a higher rate, then cheaper).
- Per-million queries, higher for latency, geo, geoproximity and IP-based routing.
- Alias queries to AWS resources are free (ELB, CloudFront, S3 website, API Gateway, VPC endpoints...).
- Health checks billed per check per month (more for HTTPS, string matching, non-AWS endpoints, fast intervals).
- Resolver endpoints billed per ENI-hour plus per query; DNS Firewall per domain list and query.
Cost tips: use aliases for AWS targets, reasonable TTLs, delete unused zones and test zones, and consolidate resolver endpoints centrally.
Hosted zone basics
- Each hosted zone has an ID (
Z0123456789ABCDEFGHIJ) used in APIs, Terraform and alias targets. - A new zone automatically gets NS and SOA records at the apex — these can't be deleted (you can edit their values/TTLs carefully).
- Records are changed through change batches (atomic sets of CREATE/DELETE/UPSERT), visible as
PENDINGthenINSYNC(aws route53 get-change), usually within 60 seconds across all Route 53 servers.