The Internet's Treasure Hunt: How Your Computer Finds Websites

 Have you ever realized that computers don't actually understand website names?

When you type https://something.com on your laptop or phone, your computer has no idea where that is. Computers only speak in numbers, specifically IP Addresses (like 192.0.2.1).

The system that translates the human name you know into the numerical address the computer needs is called DNS (Domain Name System).

Look at the diagram below. It might look like a confusing map of arrows, but it’s actually a very organized treasure hunt. Let’s break down the story of how your request travels through this map using an analogy of trying to find a specific room on a giant school campus.



Step 1: The Quick Check (The DNS Cache)

Look at the stick figure on the left. That’s you trying to go to something.com.

Before your computer goes out to the internet, it does the equivalent of checking its own pockets. It looks in the DNS Cache (that first diamond shape).

  • The Analogy: Imagine you need to find Mr. Ram's classroom. Before you walk all the way to the main office to ask, you check your own notebook. Did you write it down yesterday?

  • The Green "Yes" Arrow: If you visited the site recently, the answer is already saved in the cache. Boom! The green arrow goes straight back to you. The website loads instantly.

Step 2: Calling in the Pros (ISP/Google DNS)

What if you've never visited the site before? You follow the red "no" arrow.

Your request gets sent out of your house to an "Internet Service Provider (ISP)" or a public service like Google DNS. This server is your personal assistant for this treasure hunt.

  • The Analogy: You don't know where Mr. Ram's room is, so you go to the School Secretary. You trust them to do the running around for you. You wait in the office while they start making calls on the school intercom.

Step 3: The Chain of Command (The Hierarchy)

Now, look at the chain of boxes on the right side of the diagram. The ISP/Google DNS server (the Secretary) doesn't know the answer off the top of their head, so they have to ask the chain of command.

A. The "Root DNS" (The Principal) The Secretary first asks the Root DNS. This server knows everything about the internet's structure but doesn't know specific addresses.

  • The Root DNS says: "I don't know where something.com is exactly. But it ends in .com, so go talk to the manager in charge of the Commercial department."

B. The "TLD" (The Department Head) The Secretary follows instructions and goes to the TLD (Top Level Domain)server for ".com".

  • The TLD says: "I don't have the specific room number, but I see here that something.com is managed by a company called Route53/GoDaddy. Here is their number."

C. The "Authoritative Server" (The Classroom Teacher) Finally, the Secretary calls the specific server managed by Route53 or GoDaddy. This is the Authoritative Server. It is the final authority and the only one guaranteed to have the answer.

  • The Authoritative Server says: "Yes, I manage something.com. The address you are looking for is 192.0.2.1."

Step 4: The Return Trip

Follow the dashed green arrow all the way from the bottom right, back up to the ISP/Google DNS.

The treasure hunt is complete! The ISP/Google DNS finally has the IP address (192.0.2.1). It does two things:

  1. It sends the address back to your computer (the stick figure) so the website can load.

  2. Crucially, it saves that answer in the DNS Cache (the first diamond).

Why save it? So that next time you (or someone else in your house) want to visit something.com, you don't have to bother the Secretary, the Principal, the Department Head, and the Teacher all over again. You just take the fast green path from Step 1!

Comments

Post a Comment

Popular posts from this blog

SOLID Principle (Quick Read)

Image
 The famous design principle comprises 5 design strategies that a developer should follow for a successful application development Single Responsibility Principle Open/ Close Principle Liskov Substitution Principle Interface Segregation Principle Dependency Inversion Single Responsibility Principle(SRP) No code unit(function/class/package) should have more than one responsibility.   Bad Ex:   Class Bird  {     String result;;    public fly(Bird bird)    {     if(bird==piegeon)       result="flys 20 meter hight";    else if(bird==hen)       result="flys 5 meter";    else        result="not measured yet";    } } This class should design such a way that it should work well for all the types of birds current design is hectic to maintain for the following reasons  difficult to test. difficult in parallel programming  understanding the code...
Read more

Building a Smart Holiday Booking System with Agent-to-Agent Communication

Image
 Building a Multi-Agent Holiday Booking System with the A2A Protocol (An MVP Approach) The world of AI is rapidly moving towards "agentic systems" — autonomous AI agents that can perform complex, multi-step tasks by collaborating with each other. The challenge, however, has always been standardization: how do you get agents built on different frameworks, by different teams, to communicate effectively? This is the problem the  Agent2Agent (A2A) protocol , an open standard, aims to solve. It provides a common language for agents to discover, communicate, and collaborate securely. In this blog post, we'll walk through a Minimum Viable Product (MVP) approach to a real-world scenario: building a holiday booking system using the A2A protocol in python. Design Architecture (MVP) The Problem: A Siloed Booking Experience Imagine a traditional holiday booking website. It might have separate sections for flights, hotels, and cabs. Each of these services is handled by a different int...
Read more

Apache kafka using kraft

Image
Getting Started with Kafka in Kraft Mode: A Step-by-Step Guide Kafka is a powerful platform for real-time data processing. Traditionally, it relied on ZooKeeper for controller election and state management. However, Kraft mode, introduced in Kafka 3.0, offers significant improvements in reliability, performance, and manageability. This blog post provides a step-by-step guide to running Kafka in Kraft mode, helping you unlock its benefits. Let's dive in! Understanding Kafka Configuration Files: Navigating the Configuration Directory: Bash cd /opt/kafka ls config/kraft This command navigates to the Kafka configuration directory and lists files specific to Kraft mode. Configuration File Breakdown: broker.properties : This file manages topic partitioning and data storage/retrieval. controller.properties : Here lies the configuration for Kraft-based leader election. server.properties : This file combines the settings of both broker.properties and controller.properties for a strea...
Read more