DNS Resolution When a Resolver Has No Knowledge of a Hostname: Root Servers vs Adjacent Servers

Verified Sources

Sep 12, 2026

When a DNS Resolver receives a query for a hostname and it has “no clue” where to find that information, the standard behavior is to start from the DNS hierarchy by contacting the Root server rather than guessing or only contacting an “adjacent” server.

In DNS, the resolver typically follows either recursive or iterative resolution. In iterative resolution, the resolver asks a root server and receives a referral (e.g., “ask the .com / .org servers next”), and then continues down the hierarchy until reaching an authoritative server for the domain.

Therefore, for the question’s intent, the correct choice is (i) server asks to the root server.

DNS Resolution (Root → TLD → Authoritative) Walkthrough

Iterative DNS Resolution When the Resolver Has No Clue

1
Step 1
The resolver first looks for an answer or referral in its local cache. If it has no relevant information, it must use the DNS hierarchy.
2
Step 2
The resolver sends a DNS query to a root server for the hostname.
3
Step 3
The root server does not directly give the final IP; it returns a referral to the relevant TLD name server (e.g., .com).
4
Step 4
The resolver queries the TLD server, which then provides a referral toward the zone’s authoritative server.
5
Step 5
The resolver contacts the authoritative server for the target domain and requests the specific DNS record (like A or AAAA).
6
Step 6
The resolver sends the final resolved result back to the client, typically caching it for future queries.

Key intuition

DNS is hierarchical: if you don’t know where a hostname’s data lives, the correct strategy is to climb the hierarchy—root → TLD → authoritative—using referrals.

Why “adjacent server” is not the standard mechanism

DNS doesn’t define resolution as “ask an adjacent server” in the network-neighborhood sense. Resolvers use cached state and the global DNS delegation hierarchy (root/TLD/authoritative) to locate the correct server.

What DNS Lookup Looks Like (Typical Flow)

Resolver starts

Receives a hostname → checks cache."

Root step

Queries a root server for the domain suffix."

TLD step

Receives a referral → queries TLD servers."

Authoritative step

Receives referral → queries authoritative server."

Answer delivered

Resolver returns A/AAAA (and handles CNAME chains if present)."

Who Provides What in DNS Resolution?

High-level roles during name resolution (conceptual).

Answer Choice Explanation (MCQ)

Knowledge Check

Question 1 of 3

Q1Single choice

A DNS resolver has no cached information for a hostname. What does it do first in the standard hierarchical lookup process?

(i) Query a root server for a referral

(ii) Query an adjacent server

(iii) Stop processing the request

(iv) Choose a random server to query

Explore Related Topics

Transparent Bridge vs Router: Identifying the NOT-True Statement

Understanding Proxy Servers: Functions, Types, and Applications

Breadth-First Search as an Uninformed Search Strategy

Breadth‑First Search (BFS) expands the shallowest frontier nodes first using a FIFO queue and does not employ any heuristic function, making it an uninformed (blind) search strategy.

Classified as uninformed search because it relies only on the problem definition, not on $h(n)$ or other estimates.
Complete for finite branching factors and optimal when all step costs are equal.
Tree‑search time and space are $O(b^{d})$ ; graph‑search runs in $O(|V|+|E|)$ time and $O(|V|)$ space.
Main weakness is exponential memory growth, so it suits shallow goals with ample memory.
If step costs vary, uniform‑cost search should be used instead of BFS.

Browse all research articles