<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>DNS on StackOnward</title><link>https://stackonward.com/tags/dns/</link><description>Recent content in DNS on StackOnward</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Fri, 11 Sep 2026 05:18:00 +0800</lastBuildDate><atom:link href="https://stackonward.com/tags/dns/index.xml" rel="self" type="application/rss+xml"/><item><title>What Happens When You Type a URL in the Browser</title><link>https://stackonward.com/posts/domain-request-flow/</link><pubDate>Fri, 11 Sep 2026 05:18:00 +0800</pubDate><guid>https://stackonward.com/posts/domain-request-flow/</guid><description>&lt;p&gt;What happens when you type a URL in the browser is a sequence of hops, not a round trip to one origin. The request usually travels through DNS, a TCP or QUIC connection, TLS, a CDN or reverse proxy, and only then the application. The HTML that comes back is not the end; the browser still fetches styles, scripts, fonts, and images. &lt;a href="https://developer.mozilla.org/en-US/docs/Learn_web_development/Getting_started/Web_standards/How_the_web_works" target="_blank" rel="noopener"&gt;MDN’s account of how the web works&lt;span class="sr-only"&gt;(opens in a new tab)&lt;/span&gt;&lt;/a&gt; lists DNS, the HTTP request, the server response, and the browser assembling the page as consecutive stages.&lt;/p&gt;</description></item></channel></rss>