<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Shahper Shahin</title>
    <description>The latest articles on DEV Community by Shahper Shahin (@shahpershahin).</description>
    <link>https://dev.to/shahpershahin</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2008368%2F0663589d-2af9-486d-bafe-edaeb8806142.jpg</url>
      <title>DEV Community: Shahper Shahin</title>
      <link>https://dev.to/shahpershahin</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/shahpershahin"/>
    <language>en</language>
    <item>
      <title>DNS 101: The Internet’s GPS for Websites</title>
      <dc:creator>Shahper Shahin</dc:creator>
      <pubDate>Sun, 07 Sep 2025 10:52:27 +0000</pubDate>
      <link>https://dev.to/shahpershahin/dns-101-the-internets-gps-for-websites-5aoj</link>
      <guid>https://dev.to/shahpershahin/dns-101-the-internets-gps-for-websites-5aoj</guid>
      <description>&lt;h3&gt;
  
  
  DNS Resolution: The Internet’s GPS (That Never Gets Lost) 🌍
&lt;/h3&gt;

&lt;p&gt;Hey fam 👋 Shahper here—your go-to nerd friend who explains tech without putting you to sleep.&lt;/p&gt;

&lt;p&gt;Let’s be real: if DNS didn’t exist, the internet would be a nightmare. Imagine trying to order Starbucks by reciting its &lt;strong&gt;latitude/longitude coordinates&lt;/strong&gt; instead of just saying “Starbucks.” Yeah, nah. That’s literally what browsing without DNS would feel like.&lt;/p&gt;




&lt;h2&gt;
  
  
  DNS = The Internet’s Contact List 📖
&lt;/h2&gt;

&lt;p&gt;Computers don’t get names. They only vibe with IP addresses—long boring numbers like &lt;code&gt;13.232.0.0/13&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;DNS (Domain Name System) is the internet’s &lt;strong&gt;contact list / phonebook&lt;/strong&gt;. You type “netflix.com,” DNS translates it into &lt;code&gt;52.84.150.21&lt;/code&gt;, and boom—you’re ready to binge.&lt;/p&gt;

&lt;p&gt;If, no DNS? You’d be walking around memorizing IPs like &lt;code&gt;157.240.241.35&lt;/code&gt; for Instagram. Sounds like a punishment, not the internet.&lt;/p&gt;




&lt;h2&gt;
  
  
  Okay But… What &lt;em&gt;Actually&lt;/em&gt; Happens When You Hit Enter? 🚀
&lt;/h2&gt;

&lt;p&gt;Let’s say you type &lt;code&gt;instagram.com&lt;/code&gt; while procrastinating. Here’s the drama behind the scenes:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fbeqwr6xv3c4emi5wtqi2.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fbeqwr6xv3c4emi5wtqi2.png" alt="A fun infographic showing DNS resolution steps with Instagram as the example, using speech bubbles and icons" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  🎯 Step 1: Browser = That Friend With Trust Issues
&lt;/h3&gt;

&lt;p&gt;First, your browser checks its &lt;strong&gt;DNS cache&lt;/strong&gt; like:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;“Have I stalked Instagram recently?”&lt;/p&gt;
&lt;/blockquote&gt;

&lt;ul&gt;
&lt;li&gt;If yes → connects instantly.&lt;/li&gt;
&lt;li&gt;If no → gotta start asking around.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  🎯 Step 2: Router = The Confused Roommate
&lt;/h3&gt;

&lt;p&gt;Your router’s like: “Uh… I don’t know, lemme ask someone smarter.” It punts the question to your ISP’s DNS.&lt;/p&gt;

&lt;h3&gt;
  
  
  🎯 Step 3: ISP DNS = The Town Gossip
&lt;/h3&gt;

&lt;p&gt;Your ISP tries its own huge directory. Sometimes it also blocks sites (👀) or injects ads (rude). If it doesn’t know either, things escalate.&lt;/p&gt;

&lt;h3&gt;
  
  
  🎯 Step 4: The DNS Detective Chain 🔎
&lt;/h3&gt;

&lt;p&gt;Now it’s like asking random people for directions until you reach the right address:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Root Server&lt;/strong&gt; → “Never heard of Instagram, but &lt;code&gt;.com&lt;/code&gt; lives that way.”&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;TLD Server&lt;/strong&gt; → “I handle &lt;code&gt;.com&lt;/code&gt;, here’s who knows Instagram specifically.”&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Authoritative Server&lt;/strong&gt; → “Found it. Instagram = &lt;code&gt;157.240.241.35&lt;/code&gt;. Don’t @ me. (🥸)”&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  🎯 Step 5: Success 🎉
&lt;/h3&gt;

&lt;p&gt;Your browser finally knows where Instagram lives. It knocks on the door, and Instagram’s servers send back the juicy content. You start scrolling reels you promised you wouldn’t.&lt;/p&gt;




&lt;h2&gt;
  
  
  Spicy DNS Plot Twists 🌶️
&lt;/h2&gt;

&lt;p&gt;💀 &lt;strong&gt;DNS Can Be Attacked&lt;/strong&gt;&lt;br&gt;
Remember the 2016 Dyn attack? Hackers slammed DNS servers so hard half the internet ghosted. Amazon, Twitter, Spotify—all down. Shows how fragile DNS actually is.&lt;br&gt;
&lt;a href="https://www.thousandeyes.com/blog/dyn-dns-ddos-attack" rel="noopener noreferrer"&gt;details of dyn attack&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;👀 &lt;strong&gt;Your DNS = A Digital Snitch&lt;/strong&gt;&lt;br&gt;
Every lookup is logged. Visit WebMD at 3 AM? ISP knows. Messy typo to a sus site? ISP knows. This is why people use Cloudflare’s &lt;code&gt;1.1.1.1&lt;/code&gt;—it doesn’t track as aggressively.&lt;/p&gt;

&lt;p&gt;🧪 &lt;strong&gt;DNS Poisoning is Real&lt;/strong&gt;&lt;br&gt;
Attackers can corrupt DNS responses so you land on fake sites. It’s like someone changing your bestie’s number in your phone so your “Hey, you up?” text goes to a scammer.&lt;/p&gt;

&lt;p&gt;🕒 &lt;strong&gt;TTL = DNS’s Expiration Date&lt;/strong&gt;&lt;br&gt;
Each DNS record has a TTL (Time To Live). Short TTL = updates quickly but causes more lookups. Long TTL = fewer lookups but slower updates. It’s basically the tradeoff between fresh milk 🥛 and UHT milk 🥫.&lt;/p&gt;




&lt;h2&gt;
  
  
  When DNS Screws Up (And It Does) 💥
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;You move your website to a new server, but half your users still hit the old one? Congrats, you’ve entered &lt;strong&gt;DNS propagation hell&lt;/strong&gt;.&lt;/li&gt;
&lt;li&gt;Discord’s 2021 outage wasn’t the servers—it was DNS. The app literally became invisible to the internet.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Pro Tips (To Flex At Meetups) 🧠
&lt;/h2&gt;

&lt;p&gt;⚡ Switch your DNS for better vibes:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Cloudflare: &lt;code&gt;1.1.1.1&lt;/code&gt; (fast + privacy)&lt;/li&gt;
&lt;li&gt;Google: &lt;code&gt;8.8.8.8&lt;/code&gt; (fast but… Google knows everything)&lt;/li&gt;
&lt;li&gt;Quad9: &lt;code&gt;9.9.9.9&lt;/code&gt; (blocks malicious sites)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;⚡ Browsers secretly do &lt;strong&gt;DNS prefetching&lt;/strong&gt;—they resolve links on a page &lt;em&gt;before&lt;/em&gt; you even click. That’s why some links feel instant.&lt;/p&gt;

&lt;p&gt;⚡ Future DNS = fully encrypted lookups:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;DNS over HTTPS (DoH)&lt;/li&gt;
&lt;li&gt;DNS over TLS (DoT)&lt;/li&gt;
&lt;li&gt;DNS over QUIC 🚀 (the Gen-Z version of DNS security).&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Final Thoughts 🌍
&lt;/h2&gt;

&lt;p&gt;DNS is the internet’s &lt;strong&gt;GPS + phonebook + gossip hotline&lt;/strong&gt; rolled into one. You don’t see it, but it’s working overtime every time you hit enter.&lt;/p&gt;

&lt;p&gt;Next time you type &lt;code&gt;youtube.com&lt;/code&gt;, just know: a whole detective-level scavenger hunt happened in milliseconds before you hit play on that video.&lt;/p&gt;

&lt;p&gt;DNS is invisible… until it breaks. Then the whole internet feels like it’s down. 💀&lt;/p&gt;

&lt;p&gt;Stay curious, stay geeky, and remember—behind every Netflix binge or IG scroll, DNS had your back. 🚀&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Find Me:&lt;/strong&gt; | &lt;strong&gt;X:&lt;/strong&gt; &lt;a href="https://x.com/shahpershahin" rel="noopener noreferrer"&gt;shahpershahin&lt;/a&gt; | &lt;strong&gt;LinkedIn:&lt;/strong&gt; &lt;a href="https://www.linkedin.com/in/shahpershahin/" rel="noopener noreferrer"&gt;shahpershahin&lt;/a&gt; | &lt;strong&gt;GitHub:&lt;/strong&gt; &lt;a href="https://github.com/ShahperShahin" rel="noopener noreferrer"&gt;shahpershahin&lt;/a&gt; |&lt;/p&gt;

</description>
      <category>dns</category>
      <category>systemdesign</category>
      <category>networking</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
