<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[DNS with Dig]]></title><description><![CDATA[DNS with Dig]]></description><link>https://dns-with-dig.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Tue, 15 Sep 2026 22:18:27 GMT</lastBuildDate><atom:link href="https://dns-with-dig.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[How DNS Resolution Works: A Deep Dive with dig]]></title><description><![CDATA[The Mystery of the Missing Website
Imagine you want to visit google.com. You type it in, and it appears.
But here is the secret: Your computer has no idea where google.com is. It doesn't know names; it only knows numbers (like 142.250.190.46).
So, ho...]]></description><link>https://dns-with-dig.hashnode.dev/dns-with-dig</link><guid isPermaLink="true">https://dns-with-dig.hashnode.dev/dns-with-dig</guid><category><![CDATA[ChaiCode]]></category><category><![CDATA[#ChaiaurCode #HiteshChoudhary #PiyushGarg #GenAICohort #GenAI #LLM #PersonaPrompting #GeminiAI #ReactJS #NextJS #Python #AIChatbot #Hashnode #PromptEngineering #Vercel #HindiEnglishBlog #DevJourney]]></category><category><![CDATA[Chaiaurcode]]></category><category><![CDATA[ChaiCohort]]></category><category><![CDATA[Cohort2026]]></category><category><![CDATA[dns]]></category><category><![CDATA[networking]]></category><category><![CDATA[computerscience]]></category><dc:creator><![CDATA[Neha Kumari]]></dc:creator><pubDate>Tue, 27 Jan 2026 18:10:39 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1769537227650/7c113723-e972-4de2-bb95-9710c054b923.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<h3 id="heading-the-mystery-of-the-missing-website"><strong>The Mystery of the Missing Website</strong></h3>
<p>Imagine you want to visit <a target="_blank" href="http://google.com"><code>google.com</code></a>. You type it in, and it appears.</p>
<p>But here is the secret: Your computer has no idea where <a target="_blank" href="http://google.com"><code>google.com</code></a> is. It doesn't know names; it only knows numbers (like <code>142.250.190.46</code>).</p>
<p>So, how does it find the number that matches the name?It doesn't have a huge list of every website on earth—that list would be too big to store. Instead, it has to go on a search.</p>
<p>It hires a <strong>Detective</strong>.</p>
<hr />
<h3 id="heading-meet-the-detective-the-recursive-resolver"><strong>Meet the Detective (The Recursive Resolver)</strong></h3>
<p>In technical terms, this "Detective" is called a <strong>Recursive Resolver</strong>. It is a service usually provided by your Internet Service Provider.</p>
<p>When you type a URL, your computer says to the Detective: <em>"Go find the number for</em> <a target="_blank" href="http://google.com"><em>google.com</em></a><em>. I’ll wait here."</em></p>
<p>The Detective doesn't know the answer, but he knows exactly who to ask. He follows a strict chain of command.</p>
<hr />
<h3 id="heading-step-1-the-information-desk-the-root-servers"><strong>Step 1: The Information Desk (The Root Servers)</strong></h3>
<p>First, the Detective goes to the global headquarters of the internet. This is called the <strong>Root</strong>.</p>
<p>The Detective asks: <em>"Excuse me, do you know where</em> <a target="_blank" href="http://google.com"><em>google.com</em></a> <em>is?"</em></p>
<p>The person at the Root desk says: <em>"I don't know exactly where Google is. But I know who manages all the</em> <strong><em>.com</em></strong> <em>websites. Go talk to the .COM Department."</em></p>
<p><strong>The Technical View:</strong> Engineers can see this conversation using a command called <code>dig</code>.</p>
<ul>
<li><p><strong>Command:</strong> <code>dig . NS</code></p>
</li>
<li><p><strong>Translation:</strong> "Hey Root (.), tell me who your Name Servers (NS) are."</p>
</li>
<li><p><strong>Result:</strong> It gives us the address of the .COM managers.</p>
</li>
</ul>
<hr />
<h3 id="heading-step-2-the-department-manager-the-tld-servers"><strong>Step 2: The Department Manager (The TLD Servers)</strong></h3>
<p>The Detective follows the instructions and goes to the <strong>.COM Department</strong>. These are the <strong>Top Level Domain (TLD)</strong> servers.</p>
<p>The Detective asks: <em>"Okay, the Root sent me. Do you know where</em> <a target="_blank" href="http://google.com"><em>google.com</em></a> <em>is?"</em></p>
<p>The Department Manager says: <em>"I have a list of every .com name, but I don't know their specific IP addresses. However, I know that Google has its own team that handles their location. Here is the address for</em> <strong><em>Google's Name Servers*</em></strong>."*</p>
<p><strong>The Technical View:</strong></p>
<ul>
<li><p><strong>Command:</strong> <code>dig com NS</code></p>
</li>
<li><p><strong>Translation:</strong> "Hey .com, tell me who manages your Name Servers."</p>
</li>
<li><p><strong>Result:</strong> It points us to Google's specific servers.</p>
</li>
</ul>
<hr />
<h3 id="heading-step-3-the-company-office-the-authoritative-servers"><strong>Step 3: The Company Office (The Authoritative Servers)</strong></h3>
<p>Finally, the Detective goes to the address given by the Department Manager. He arrives at <strong>Google’s own servers</strong>. These are called the <strong>Authoritative Servers</strong>. They are the "Authority"—the boss who knows the final answer.</p>
<p>The Detective asks: <em>"I've been sent by the Root and the .COM manager. I need the address for</em> <a target="_blank" href="http://google.com"><em>google.com</em></a><em>."</em></p>
<p>The Google Server says: <em>"You've come to the right place. The address is</em> <strong><em>142.250.190.46*</em></strong>."*</p>
<p><strong>The Technical View:</strong></p>
<ul>
<li><p><strong>Command:</strong> <code>dig</code> <a target="_blank" href="http://google.com"><code>google.com</code></a> <code>NS</code></p>
</li>
<li><p><strong>Translation:</strong> "Hey Google, show me your official Name Servers."</p>
</li>
<li><p><strong>Result:</strong> Confirms we are at the source of truth.</p>
</li>
</ul>
<hr />
<h3 id="heading-step-4-the-final-answer"><strong>Step 4: The Final Answer</strong></h3>
<p>The Detective writes down <code>142.250.190.46</code> and runs back to your computer.</p>
<ul>
<li><p><strong>Detective:</strong> <em>"Here is the number you asked for!"</em></p>
</li>
<li><p><strong>Your Computer:</strong> <em>"Thanks!"</em> (And connects you to the website).</p>
</li>
</ul>
<p><strong>The Technical View:</strong></p>
<ul>
<li><p><strong>Command:</strong> <code>dig</code> <a target="_blank" href="http://google.com"><code>google.com</code></a></p>
</li>
<li><p><strong>Translation:</strong> "Just give me the answer."</p>
</li>
<li><p><strong>Result:</strong> <code>142.250.190.46</code> (The IP Address).</p>
</li>
</ul>
<hr />
<h3 id="heading-summary"><strong>Summary</strong></h3>
<p>The entire internet is built on this simple chain of referrals. No one knows everything, but everyone knows who to ask next.</p>
<ol>
<li><p><strong>You ask the Detective</strong> (Resolver).</p>
</li>
<li><p><strong>Detective asks the Root</strong> ("Who runs .com?").</p>
</li>
<li><p><strong>Detective asks the TLD</strong> ("Who runs Google?").</p>
</li>
<li><p><strong>Detective asks Google</strong> ("What is your IP?").</p>
</li>
</ol>
<p>This entire conversation happens in milliseconds—faster than the blink of an eye. That is the magic of DNS.</p>
]]></content:encoded></item></channel></rss>