Have you ever wondered what happens behind the scenes when you type a website name into your browser? Whether you are looking for study materials, watching videos, or shopping online, your computer must first find the correct server before loading the webpage. This process is made possible by the Domain Name System (DNS).

To understand how DNS works, let us follow a simple story and then look at the full process architecture.

A Boy Searching for a Math Book PDF

A boy has been assigned several math exercises by his teacher. When he gets home, he realizes that he has misplaced his math book. Instead of giving up, he decides to search for a Math Book PDF online.

He opens his laptop and types www.mathbookpdf.com into his web browser. Although he knows the website’s name, he does not know its numerical IP address—the unique address that identifies the website’s server on the internet. Just as people use names instead of phone numbers to identify contacts, we use domain names because they are much easier to remember than IP addresses.

However, computers cannot communicate using domain names alone. They need an IP address to locate and connect to the correct web server. This is where DNS comes into play.

Step 1: Checking the Local DNS Cache

As soon as the boy presses Enter, his computer first checks its DNS cache. The cache stores the IP addresses of websites that have been visited recently.

If the IP address is already stored in the cache, the computer immediately connects to the website without performing another DNS lookup. Since the boy is visiting this website for the first time, the required IP address is not available, so the computer must ask the DNS system for help.

Step 2: Asking the DNS Resolver

The request is sent to a DNS Resolver (DNS Recursor). Think of the resolver as a knowledgeable librarian whose job is to help locate information. The resolver searches on behalf of the user’s computer until it finds the correct IP address.

Because the resolver does not already know the answer, it begins a step-by-step search.

Step 3: Contacting the Root Nameserver

The resolver first contacts a Root Nameserver.

The Root Nameserver functions like a master directory. It does not know the exact IP address of the requested website, but it knows where to continue the search. Based on the website’s ending, such as .com, .org, or .edu, it directs the resolver to the appropriate Top-Level Domain (TLD) Nameserver.

Step 4: Querying the TLD Nameserver

Next, the resolver contacts the Top-Level Domain (TLD) Nameserver responsible for the website’s domain extension.

Since the boy entered www.mathbookpdf.com, the resolver contacts the .com TLD Nameserver. This server manages information about websites ending in .com. While it still does not know the website’s IP address, it knows which Authoritative Nameserver is responsible for that specific domain.

Step 5: Reaching the Authoritative Nameserver

The resolver then sends a request to the Authoritative Nameserver.

This server stores the official DNS records for the domain. These records include the website’s A Record for IPv4 or AAAA Record for IPv6, which map the domain name to its IP address.

Here is the domain-to-IP mapping in a simple visual form:

+------------------------------+
|        DOMAIN NAME           |
|     www.mathbookpdf.com      |
+--------------+---------------+
               |
               v
+------------------------------+
|         DNS RECORD           |
|        A / AAAA Record       |
+--------------+---------------+
               |
               v
+------------------------------+
|         IP ADDRESS           |
|       203.0.113.25           |
+------------------------------+

The Authoritative Nameserver returns the correct IP address to the DNS Resolver.

Step 6: Returning the IP Address

After receiving the IP address, the DNS Resolver sends it back to the boy’s computer. It also stores the result in its cache so that future requests for the same website can be answered much more quickly.

Now the browser knows exactly where the website is located.

Step 7: Connecting to the Website

Using the returned IP address, the browser establishes a connection with the web server hosting www.mathbookpdf.com.

The server responds by sending the webpage and its contents back to the browser. Within a few moments, the boy sees the website on his screen, downloads the Math Book PDF, and begins completing his homework.

Full DNS Architecture Flow

To make the entire process even clearer, here is the complete architecture in one continuous flow:

+---------------+
| USER/BROWSER  |
| Types Domain  |
| www.mathbook  |
| pdf.com       |
+-------+-------+
        | DNS Query
        v
+--------------------+
| LOCAL DNS CACHE    |
| Browser / OS Cache |
+-------+------------+
        |
   Cache Hit?
   +----+-----+
   |          |
 Yes         No
   |          |
   |          v
   |   +--------------------+
   |   | DNS RESOLVER       |
   |   | ISP / Public DNS   |
   |   +-------+------------+
   |           |
   |           v
   |   +--------------------+
   |   | ROOT NAMESERVER    |
   |   | "Go to .com TLD"   |
   |   +-------+------------+
   |           |
   |           v
   |   +--------------------+
   |   | .COM TLD           |
   |   | NAMESERVER         |
   |   | Finds Authority    |
   |   +-------+------------+
   |           |
   |           v
   |   +--------------------+
   |   | AUTHORITATIVE      |
   |   | NAMESERVER         |
   |   |                    |
   |   | A -> 203.0.113.25   |
   |   | AAAA -> 2001:db8::25|
   |   +-------+------------+
   |           |
   |           v
   |   +--------------------+
   |   | RETURN IP ADDRESS  |
   |   | Cache at Resolver  |
   |   +-------+------------+
   +-----------+
        |
        v
+--------------------+
| BROWSER RECEIVES   |
| 203.0.113.25       |
+-------+------------+
        | HTTPS / HTTP
        v
+--------------------+
| WEB SERVER         |
| Hosts Website      |
+-------+------------+
        | HTML • CSS • JS
        v
+--------------------+
| WEBSITE LOADS      |
| Math Book PDF Page |
+--------------------+

Why DNS Is Important

Without DNS, users would need to remember the numerical IP address of every website they visit. For example, instead of typing an easy-to-remember domain name, they would have to enter something like 203.0.113.25 every time they wanted to access a website.

DNS acts as the internet’s phonebook by translating human-readable domain names into machine-readable IP addresses. This translation allows users to access websites quickly and conveniently without needing to remember complex numbers.

Conclusion

Every time you enter a website’s domain name, a series of DNS servers work together behind the scenes to locate the correct IP address. The computer first checks its cache, then consults the DNS Resolver, Root Nameserver, TLD Nameserver, and finally the Authoritative Nameserver. Once the IP address is found, the browser connects to the web server and loads the requested website.

Although this entire process usually takes only a few milliseconds, it is one of the most essential operations that makes the modern internet work. Without DNS, browsing the web would be far less convenient, requiring users to memorize IP addresses instead of simple, memorable domain names.

Home/Blogs

Share to...

Scan QR Code

Install The Ripper

Scan QR Code