Describe how DNS resolution works.
Interviewer Expectations for this Question
01
Core Competency
Assesses fundamental understanding of Computer Networks conventions, runtime behavior, and memory/performance considerations.
02
Evaluation Criteria
Hiring managers look for precision, avoidance of ambiguous jargon, and ability to explain trade-offs under real production conditions.
Comprehensive Model Answer
Verified Solution
DNS maps names to records, most importantly A and AAAA addresses, plus CNAME, MX, TXT and NS. A lookup can walk several servers, but caching means most lookups stop early.
Resolution steps:
- Check the local hosts file and OS resolver cache.
- Query the configured recursive resolver, often via the ISP or a public service.
- If not cached, the resolver asks a root server, which points to the top-level domain servers.
- The TLD server points to the domain's authoritative name servers.
- The authoritative server returns the record; the resolver caches it for its TTL and answers the client.
Queries use UDP port 53, falling back to TCP for large responses, and DoT or DoH when encryption is wanted.
client -> recursive resolver -> root -> .com -> ns.example.com
Caching and TTLs reduce load and latency. Debug with dig +trace or nslookup, and remember that propagation delays are really cache expiry.
Candidate Response Strategy & Interview Tips
- Start with a concise one-sentence summary: Deliver a direct, confident answer first before expanding into nuances.
- Demonstrate real-world trade-offs: Discuss where this approach excels and when you would avoid it in production systems.
- Discuss complexity & edge cases: Proactively explain time/space complexity or boundary conditions (null values, scale limits).
- Prepare for interviewer follow-ups: Technical hiring panels frequently probe deeper into concurrency, backward compatibility, or alternative libraries.