Opscraft
Route 53 hosted zones · Lesson 8 of 8 · 3 min read

Interview questions and model answers

"Public vs private hosted zone?"

A public hosted zone is authoritative on the internet via its four Route 53 name servers registered at the registrar. A private hosted zone answers only queries arriving through the Route 53 Resolver from VPCs associated with it — across accounts and regions if you associate them — and isn't visible publicly.

"How do EC2 instances resolve a private hosted zone record?"

They query the VPC's Route 53 Resolver at the base-plus-two address or 169.254.169.253, which answers from private hosted zones associated with that VPC, provided DNS support and DNS hostnames are enabled and the instance uses the Amazon-provided resolver via the DHCP options set.

"What is split-horizon DNS and what are the pitfalls?"

Hosting the same domain in a public and a private zone so internal clients get internal endpoints and external clients get public ones — for example api.example.com pointing to an internal ALB inside the VPC and the public ALB outside. The main pitfall is that private zones don't fall back to public ones, so every needed name must exist in both; also two sources of truth and debugging confusion. Using a dedicated internal subdomain avoids most of this.

"Design DNS for on-prem plus multiple AWS accounts."

A central networking account with inbound and outbound Route 53 Resolver endpoints in multiple AZs. On-prem DNS conditionally forwards our AWS internal domains to the inbound endpoints. Outbound forwarding rules send on-prem domains to on-prem DNS servers and are shared to workload accounts with RAM. Private hosted zones for shared services are associated with spoke VPCs, ideally via Route 53 Profiles. Add Resolver query logging and DNS Firewall for security, and manage everything with Terraform.

"A pod resolves private names but a Lambda in the same VPC doesn't. Why?"

The Lambda probably isn't attached to the VPC — without VPC configuration it uses AWS's public resolution and can't see private hosted zones. Attaching it to the VPC's subnets makes it use the VPC resolver.

"How would you automate DNS for 50 microservices on EKS?"

External DNS running with a least-privilege IRSA role scoped to our hosted zones, domain filters and a TXT owner ID per cluster, creating records from Ingress or Service annotations. Manifests live in Git and are applied by Flux, so DNS changes are reviewed and follow deployments automatically.

"What breaks if enableDnsSupport is false?"

The Amazon-provided resolver stops answering for that VPC entirely — instances can't resolve private zones, VPC-internal names or even public names via the VPC resolver, and private DNS for interface endpoints stops working.