DNS and how domain resolution works in HLD - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does DNS stand for and what is its main purpose?

DNS stands for Domain Name System. Its main purpose is to translate human-friendly domain names (like example.com) into IP addresses that computers use to identify each other on the network.

intermediate

What is a recursive DNS resolver?

A recursive DNS resolver is a server that receives a DNS query from a client and then takes the responsibility to find the IP address by querying other DNS servers until it gets the answer or an error.

intermediate

Explain the role of root DNS servers in domain resolution.

Root DNS servers are the first step in the DNS lookup process. They don’t know the exact IP but direct the resolver to the appropriate Top-Level Domain (TLD) servers, like those for .com or .org domains.

beginner

What is caching in DNS and why is it important?

Caching in DNS means storing the results of previous DNS queries temporarily. It is important because it speeds up domain resolution and reduces the load on DNS servers by avoiding repeated lookups for the same domain.

intermediate

Describe the difference between authoritative DNS servers and recursive resolvers.

Authoritative DNS servers hold the actual DNS records for domains and provide definitive answers. Recursive resolvers act as intermediaries that query authoritative servers on behalf of clients to find the IP address.

What is the first step a recursive resolver takes when resolving a domain name?

A Query the root DNS servers

B Query the authoritative DNS server

C Return cached IP address

D Send a request to the client

The recursive resolver starts by querying the root DNS servers to find the TLD servers responsible for the domain.

Which DNS server type holds the actual DNS records for a domain?

A Recursive resolver

B Root server

C Authoritative DNS server

D Caching server

Authoritative DNS servers store the real DNS records and provide final answers for domain queries.

Why is DNS caching beneficial?

A It reduces DNS server load and speeds up lookups

B It slows down domain resolution

C It deletes old DNS records

D It increases the number of DNS queries

Caching reduces repeated queries and speeds up the resolution process by storing previous results temporarily.

What does a TLD DNS server do during domain resolution?

A Directs queries to root servers

B Provides IP addresses for all domains

C Caches DNS queries

D Directs queries to authoritative DNS servers for specific domains

TLD servers direct the resolver to the authoritative DNS servers responsible for the specific domain.

Which of the following is NOT part of the DNS resolution process?

A Client sends DNS query

B Client directly queries authoritative DNS servers

C Recursive resolver queries authoritative servers

D Recursive resolver queries root servers

Clients usually query recursive resolvers, not authoritative servers directly.

Explain the step-by-step process of how a domain name is resolved to an IP address using DNS.

Think of it like asking a series of helpers until you find the right address.

Describe the roles of recursive resolvers, root servers, TLD servers, and authoritative servers in DNS.

Imagine a chain of helpers passing your question along until the answer is found.

Practice

1. What is the main purpose of DNS in internet communication?

easy

A. To translate domain names into IP addresses

B. To store website content

C. To encrypt internet traffic

D. To manage email delivery

Solution

1. Step 1: Understand DNS role

   DNS stands for Domain Name System and its main job is to convert human-friendly domain names into IP addresses computers use.

2. Step 2: Identify correct function

   Among the options, only translating domain names to IP addresses matches DNS's core function.

3. Final Answer:

   To translate domain names into IP addresses -> Option A

4. Quick Check:

   DNS = domain to IP translation [OK]

Hint: DNS converts names to IPs, not content or encryption [OK]

Common Mistakes:

• Confusing DNS with web hosting
• Thinking DNS encrypts data
• Mixing DNS with email servers

2. Which of the following is the correct order of DNS resolution steps when a user types a domain name?

easy

A. Root server -> TLD server -> Authoritative server

B. Authoritative server -> Root server -> TLD server

C. TLD server -> Root server -> Authoritative server

D. Local cache -> Authoritative server -> Root server

Solution

1. Step 1: Recall DNS resolution hierarchy

   DNS resolution starts at the root server, then goes to the TLD (Top-Level Domain) server, and finally to the authoritative server for the domain.

2. Step 2: Match the correct sequence

   Root server -> TLD server -> Authoritative server correctly lists the order: Root -> TLD -> Authoritative.

3. Final Answer:

   Root server -> TLD server -> Authoritative server -> Option A

4. Quick Check:

   Resolution order = Root, TLD, Authoritative [OK]

Hint: DNS starts at root, then TLD, then authoritative [OK]

Common Mistakes:

• Mixing up the order of servers
• Starting resolution at authoritative server
• Ignoring the root server step

3. Consider this simplified DNS resolution code snippet:

cache = {"example.com": "93.184.216.34"}

query = "example.com"

if query in cache:
    ip = cache[query]
else:
    ip = "198.51.100.1"  # IP from authoritative server

print(ip)

What will be the output when this code runs?

medium

A. 198.51.100.1

B. example.com

C. 93.184.216.34

D. KeyError

Solution

1. Step 1: Check if query is in cache

   The query is "example.com" which exists in the cache dictionary with IP "93.184.216.34".

2. Step 2: Determine printed IP

   Since the query is found in cache, the code assigns ip = cache[query] which is "93.184.216.34" and prints it.

3. Final Answer:

   93.184.216.34 -> Option C

4. Quick Check:

   Cache hit returns cached IP [OK]

Hint: If domain in cache, output cached IP [OK]

Common Mistakes:

• Assuming authoritative IP prints always
• Confusing key and value in dictionary
• Expecting error if key exists

4. A DNS resolver is not returning the correct IP address for a domain. Which of the following is the most likely cause?

medium

A. The domain name is misspelled in the URL

B. The root server is unreachable but TLD server works

C. The authoritative server is down but cache is fresh

D. The local DNS cache has outdated information

Solution

1. Step 1: Analyze DNS caching impact

   If the local DNS cache holds old IP data, the resolver returns outdated IP even if authoritative server changed.

2. Step 2: Evaluate other options

   Misspelled domain would cause failure, not wrong IP. Authoritative down with fresh cache returns correct IP. Root unreachable but TLD working is unlikely scenario causing wrong IP.

3. Final Answer:

   The local DNS cache has outdated information -> Option D

4. Quick Check:

   Outdated cache causes wrong IP [OK]

Hint: Old cache causes wrong IP, refresh fixes it [OK]

Common Mistakes:

• Ignoring cache as source of error
• Assuming authoritative server always reachable
• Confusing root and TLD server roles

5. You want to design a scalable DNS system for a global service. Which approach best improves DNS resolution speed and reduces load on authoritative servers?

hard

A. Use a single global authoritative server for all domains

B. Implement multiple caching layers including local resolver and CDN caches

C. Direct all DNS queries only to the authoritative servers

D. Disable caching to always get fresh IP addresses

Solution

1. Step 1: Understand scalability needs

   To handle many users globally, caching at multiple layers reduces repeated queries to authoritative servers and speeds up responses.

2. Step 2: Evaluate options for load and speed

   Direct queries to authoritative servers increase load and latency. Single global server is a bottleneck and risk. Disabling caching slows resolution and increases load.

3. Final Answer:

   Implement multiple caching layers including local resolver and CDN caches -> Option B

4. Quick Check:

   Multi-layer caching improves speed and scalability [OK]

Hint: Use caching layers to scale DNS efficiently [OK]

Common Mistakes:

• Ignoring caching benefits
• Centralizing authoritative servers causing bottlenecks
• Disabling caching for freshness without tradeoff