Interview questions and model answers
"What is the SOA record and what are its fields?"
Start of Authority — one per zone, at the apex. It names the primary name server (MNAME) and the admin email with the at-sign as a dot (RNAME), and holds the serial, refresh, retry, expire and minimum values. Secondaries poll the serial every refresh interval and transfer the zone when it increases, retry on failure, and stop answering if they can't reach the primary for the expire period. The minimum field today sets the negative-caching TTL for NXDOMAIN answers.
"What's the difference between authoritative and recursive DNS servers?"
Authoritative servers hold a zone's records and give definitive answers with the aa flag; they don't look things up for clients. Recursive resolvers do the lookups on behalf of clients — root, TLD, authoritative — and cache results for the TTL. Route 53 hosted zones are authoritative; the Route 53 Resolver in a VPC, 8.8.8.8, and CoreDNS's forwarding are recursive.
"What are glue records and when do you need them?"
Address records for name servers published by the parent zone in the referral. They're needed when the name servers are inside the zone they serve — ns1.example.com for example.com — otherwise resolvers couldn't find the name servers without already resolving the zone. Route 53's name servers live in other domains, so no glue is needed.
"I created a Route 53 hosted zone but the domain still uses the old DNS. Why?"
The registrar still delegates to the old name servers. The world finds a zone through the parent's NS records, so I'd update the name servers at the registrar to the hosted zone's four Route 53 servers, after making sure all records exist in the new zone, and keep the old provider serving for about 48 hours because the TLD's NS TTL is typically two days.
"Why does Route 53 give four name servers on different TLDs?"
Resilience: they're anycast across AWS's edge network, and spreading the names across .com, .net, .org and .co.uk means an issue with one TLD's infrastructure can't make the zone unreachable.
"How do you let a team manage dev.example.com in their own account?"
Create a hosted zone for dev.example.com in their account and add an NS record set for dev.example.com in the parent zone with that zone's four name servers. Delegation splits ownership cleanly with separate IAM.
"How would you protect against a DNS provider outage?"
Multi-provider authoritative DNS: records defined in code and pushed to two providers, both providers' name servers listed at the registrar, and avoiding provider-specific features on critical names. Plus monitoring from multiple locations, sensible TTLs, and registrar security — lock, MFA, auto-renew.
"What is a lame delegation?"
An NS record pointing to a server that isn't authoritative for the zone — decommissioned, misconfigured or a deleted hosted zone. Resolvers that try it get errors or timeouts, causing intermittent SERVFAIL or slow lookups. Fix the NS set at the parent and child so every listed server serves the zone.