How DNS Resolution Works

Question

Walk me through the steps when you type a URL into your browser and press enter.

Accepted Answer

When you type a URL into your browser and press enter, a sophisticated sequence of events involving your browser, operating system, and various network protocols unfolds to fetch and display the webpage. Let me walk you through the key steps involved in this process. **1. Browser Cache and HSTS Lookup:** The browser first checks its internal cache (both memory and disk) for any cached resources related to the URL, including the HTML, CSS, JavaScript, and images. It also checks its HSTS (HTTP Strict Transport Security) preload list to determine if the domain should only be accessed via HTTPS, even if HTTP was initially typed. **2. OS Resolver Cache and Hosts File Check:** If the resource isn't found in the browser's cache, the browser then queries the operating system's DNS resolver cache. Simultaneously, it checks the local 'hosts' file (e.g., `/etc/hosts` on Linux/macOS or `C:\Windows\System32\drivers\etc\hosts` on Windows) to see if there's a static IP address mapping for the domain. **3. Recursive DNS Resolution:** If no local IP address is found, the OS's DNS resolver initiates a recursive query to its configured DNS server (often provided by your ISP or a public DNS service like 8.8.8.8). This resolver then performs an iterative query sequence: it contacts a root server, which directs it to a Top-Level Domain (TLD) server (e.g., .com), which finally directs it to the authoritative nameserver for the specific domain, which provides the IP address. This IP is then returned to the OS resolver and cached. **4. TCP Connection and TLS Handshake:** With the resolved IP address, the browser initiates a TCP three-way handshake (SYN, SYN-ACK, ACK) with the web server on the specified port (typically 80 for HTTP, 443 for HTTPS). If the URL uses HTTPS, a critical TLS/SSL handshake occurs immediately after the TCP connection to establish a secure, encrypted communication channel before any application-level data is exchanged. **5. HTTP/HTTPS Request, Server Processing, and Rendering:** The browser then sends an HTTP (or encrypted HTTPS) request (e.g., GET /index.html) for the webpage. The web server processes this request, retrieves the necessary resources, and sends an HTTP/HTTPS response back, including the status code (e.g., 200 OK) and the webpage content. Finally, the browser parses the received HTML, CSS, and JavaScript, builds the DOM (Document Object Model), and renders the webpage on your screen, potentially initiating further requests for embedded resources like images or external stylesheets. Understanding this intricate sequence is fundamental for network troubleshooting, optimizing web performance, and ensuring the reliability and security of web applications. It highlights the numerous layers involved from a simple URL input to a fully rendered webpage.

How DNS Resolution Works

Ready to prove your AWS networking knowledge?

DNS A Record vs CNAME

DNS Propagation Basics

Purpose of a CDN

DNS Resolution Failure

Clients Using Stale DNS Cache

Paginated vs. Bulk API Calls: Performance, Cost, and Reliability Trade‑offs

EKS Cluster Upgrades: A Production Runbook for Platform Teams