Chintu kahan rehta hai (google.com → IP address)

Ab khabar aayi hai
Chintu ki shaadi hai
Aur woh bhi love marriage ❤️

Hum uski shaadi attend karna chahte hain.
Gift bhi le jaana hai. Aur time pe pahunchna bhi zaroori hai.

Lekin ek sawaal hai:

→ Uske ghar jaayenge kaise?

Bilkul yahi sawaal internet bhi poochta hai jab data bhejna hota hai.

Internet Ko Rules (Protocol) Kyun Chahiye?

The internet needs rules to send data correctly. Without rules, data would get lost, mixed up, or arrive incomplete.

These rules are called protocols.

Aaj hum teen protocols samjhenge:

• TCP

• UDP

• HTTP

Do Raaste:

Chintu ke ghar jaane ke liye do raaste hain:

• ek safe road

• ek fast shortcut

Internet mein bhi data bhejne ke do main tareeke hote hain:

• TCP

• UDP

TCP Kya Hai?

TCP (Transmission Control Protocol) is a reliable and safe protocol.
It guarantees that data:

• reaches the destination

• arrives in the correct order

• TCP resent it if lost

TCP aur Shaadi Ka Gift

Socho tum Chintu ke liye shaadi ka gift bhej rahe ho.
Tum kahoge:

Gift kahin kho na jaaye.

Isliye tum courier service use karoge:

• tracking milegi

• confirmation milega

• gift safe pahuchega

Yeh bilkul TCP jaisa behaviour hai.

When to Use TCP

English
Use TCP when data is important and cannot be lost.

Examples:

• Login / Signup

• Online payments

• File download

• Email

• Form submission

UDP Kya Hai?

UDP (User Datagram Protocol) is a fast but unreliable protocol.
It sends data without waiting for confirmation.

UDP aur Shaadi Ka DJ

Chintu ki shaadi mein:

• DJ music chal raha hai

• log dance kar rahe hain

Agar:

• ek beat miss ho jaaye

• ek video frame chhoot jaaye

Koi badi baat nahi.

Par agar music ruk-ruk ke aaye. Shaadi ka maza kharab ho jaata hai.

Isliye yahan speed zyada important hai, aur UDP best hota hai.

When to Use UDP

Use UDP when speed matters more than reliability.

Examples:

• Video streaming

• Online gaming

• Voice / video calls

• Live sports

HTTP Kya Hai?

HTTP is an application-level protocol.
It defines how browsers and servers communicate.

HTTP decides:

• what request to send

• what response to receive

HTTP yeh nahi batata ki data kaise safely pahuchega.

HTTP aur Shaadi Ka Invitation

Chintu ne shaadi ka invitation likha:

• language decide ki

• format decide ki

Invitation kya likhna hai → HTTP
Invitation kaise safely bhejna hai → TCP

HTTP aur TCP Ka Relationship

HTTP runs on top of TCP.
TCP handles delivery, HTTP handles communication.

HTTP → kya bolna hai
TCP  → kaise bhejna hai
IP   → kahan bhejna hai

Final Conclusion:

DNS batata hai kahan jaana hai
TCP/UDP batate hain kaise jaana hai
HTTP batata hai kya baat karni hai

What’s Next?

Chintu ki shaadi toh mast ho gayi
Gift bhi time pe pahunch gaya
DJ bhi bina ruke bajta raha

• Lekin ek baat socho

  → Gift pahunchne se pehle Chintu ne phone pe “Hello, sun rahe ho?” kyun bola?
  → Aur saamne wale ne “Haan bhai, bolo” kyu kaha?

  Internet bhi bilkul yahi karta hai.

  Data bhejne se pehle TCP pehle baat clear karta hai,
  seedha kuch bhi bhej deta nahi.

  Agla article mein hum Chintu aur Internet ki first call sunenge
  Jahan:

  • “Hello” = SYN

  • “Haan, sun raha hoon” = SYN-ACK

  • “Theek hai, shuru karte hain” = ACK

TCP ka famous 3-Way Handshake, next article mei

Bye…

Hello!
Aaj hum Chintu ka ghar dhundhne ja rahe hain, aur is journey mein aap CID banoge

In the last blog, we learned about DNS records, also called the phonebook of the internet. Aaj hum ek level aur deep jaayenge.

When you type a website name in your browser, your computer doesn’t know where that website lives.
It has to ask around. This step-by-step process of asking is called DNS Resolution.

Let’s understand this with a simple story.

What Is DNS Resolution?

Imagine this situation

You want to go to Chintu’s house, but you don’t know the address.

You only know one thing:
Chintu ka naam.

DNS Resolution is exactly this process:

Finding the address (IP) using the name (domain).

• Humans understand names → google.com

• Computers understand numbers → 142.150.XX.XX

DNS helps convert names into number.

The Story: Finding Chintu’s House

Let’s start asking people.

Step 1: Asking the Root (The Top Boss)

First, you go to the biggest office in the world and ask:

Do you know where Chintu lives?

The boss replies:

Mujhe exact ghar nahi pata,
but mujhe pata hai kaun .com area handle karta hai.

These are called Root Name Servers. There are 13 logical root servers in the world.

Command

dig . NS

• . means root

• NS means Name Servers (who is responsible?) (Kaun sa server google.com ka record sambhal raha hai?)

Important:

• Root servers don’t know website IPs

• They only give directions

Step 2: Asking the .com Office (TLD Servers)

Now you go to the .com office and ask:

Do you know where google.com is?

They say:

Exact address nahi pata,
but mujhe pata hai kaun Google ko handle karta hai.

These are called TLD (Top-Level Domain) Servers.

Command

dig com NS

Their job:

• Handle all .com domains

• Tell you who owns which domain

Step 3: Asking Google’s Own Office (Authoritative Servers)

Now we are very close.

You ask:

Bhai, google.com ka exact address batao.

This time, you are talking to Google’s own DNS servers.

These are called Authoritative Name Servers.

Command

dig google.com NS

They reply:

ns1.google.com
ns2.google.com
ns3.google.com
ns4.google.com

Important:

• These servers are controlled by Google

• Whatever they say is final truth

Step 4: Getting the Final Address (IP Address)

Now we ask the final question:

Chintu ka ghar exactly kahan hai?

Command

dig google.com

(Default: asks for A record)

Result

You get IP addresses like:

142.250.xxx.xxx

Mission successful!
We found Chintu’s house.

Now the browser knows where to send the request.

Iterative vs Recursive

You might be thinking:

Kya browser har baar itna bhagta hai?

No
There are two ways DNS resolution works.

Iterative Resolution (What We Just Did)

We personally:

• asked Root

• then TLD

• then Authoritative

This is called Iterative Resolution.

Recursive Resolution (Real Life)

In real life, your browser says to a DNS server (ISP / 8.8.8.8):

Boss, tum hi IP dhundh ke do.

That DNS server:

• runs around the internet

• talks to Root, TLD, Authoritative

• caches the answer

• gives you the final IP

Browser waits peacefully.
DNS resolver does all the mehnat

Simple Mental Model (Remember This)

Root (.)        → “Ask .com”
TLD (.com)     → “Ask Google”
Authoritative  → “Here is the IP”

DNS is not magic.
It’s well-organized delegation.

What’s Next?

Finally! Chintu ka ghar mil gaya

But… ruk jao zara

Address mil jaana sirf half kaam hai. Ab sawaal yeh hai:

Wahan jaayenge kaise?

• Family car: safe, seatbelt laga hua,
  har step pe confirmation milta hai (TCP)

• Shortcut wali ride: fast, thrilling,
  par thoda risky bhi (UDP)

Internet par bhi bilkul aisa hi hota hai.
Har situation ke liye same raasta best nahi hota.

→ DNS batata hai kahan jaana hai,
TCP aur UDP decide karte hain kaise jaana hai.

Next blog mein, hum samjhenge
kab kaunsa raasta choose karna chahiye real-life examples ke saath.

Bye….

How does the browser know where Google’s website is actually located?

Computers don’t understand website names like humans do.
They understand numbers, called IP addresses, like:

142.250.183.206

So the big question is:

How does google.com turn into an IP address?

That’s where DNS comes in.

What Is DNS?

DNS (Domain Name System) is the phonebook of the internet.

• Humans remember names → google.com

• Computers need numbers → 142.250.183.206

DNS converts names into numbers.

Real-Life Example

Think of DNS like your phone contacts:

• You tap “Mom”

• Your phone secretly dials her phone number

• You don’t remember the number DNS remembers it

Why Do We Need DNS Records?

DNS doesn’t store just one thing.

A domain needs information about:

• Where the website lives

• Where emails should go

• Who controls the domain

• Security and verification

DNS records are instructions that tell the internet what to do with your domain.

What Is an NS Record? (Who Is Responsible for the Domain)

NS = Name Server

An NS record answers one simple question:

“Who is in charge of this domain?”

NS records tell the internet:

Which DNS servers manage example.com

Without NS records → nothing works

What Is an A Record? (Domain → IPv4 Address)

A = Address

An A record maps:

example.com → 93.184.216.34

Real-Life Example

• Website name = person’s name

• IP address = house address

When someone visits your website:

1. Browser asks DNS: “Where does this domain live?”

2. A record replies with the IPv4 address

This is the most important DNS record for websites

What Is an AAAA Record? (Domain → IPv6 Address)

AAAA record is the IPv6 version of A record.

• IPv4 example: 93.184.216.34

• IPv6 example:
  2606:2800:220:1:248:1893:25c8:1946

Why Do We Need This?

We are running out of IPv4 addresses
IPv6 gives us a lot more addresses.

Browser behavior:

• If IPv6 is available → uses AAAA

• Otherwise → uses A record

What Is a CNAME Record? (One Name Points to Another)

CNAME = Canonical Name

A CNAME record makes one domain point to another domain.

Example:

www.example.com → example.com

What Is an MX Record? (How Emails Find Your Mail Server)

MX = Mail Exchange

MX records answer:

“Where should emails for this domain go?”

Example:

example.com → mail.google.com

Real-Life Example

Your house has:

• Home address (website)

• Post office (email server)

Web traffic and email traffic go to different places.

Important Clarification

• NS → who manages DNS

• MX → who handles email

They are not the same.

What Is a TXT Record? (Verification & Security)

TXT records store text information.

Used for:

• Domain ownership verification

• Email security (SPF, DKIM, DMARC)

• Connecting services (Google, GitHub, AWS)

How All DNS Records Work Together (One Example)

Let’s take mywebsite.com

Behind the scenes:

NS Record
→ Who manages the domain

A / AAAA Record
→ Where the website lives

CNAME Record
→ Makes www.mywebsite.com work

MX Record
→ Routes emails correctly

TXT Record
→ Verifies ownership & secures email

Summary

Conclusion:

Without DNS records:
- Websites wouldn’t load
- Emails wouldn’t arrive

DNS quietly makes the internet usable every day

Think of the internet like a huge city with many roads.

When you open a website or use an app:

• Data starts from your laptop or phone

• Travels through cables and network devices

• Reaches a server

• Comes back with a response

Before your data reaches your app, it passes through these devices:

• Modem

• Router

• Firewall

• Load Balancer

• Switch

Each device has one clear job.

1. What Is a Modem?

Modem = Connection to the Internet

Your Internet Service Provider (ISP) sends data in a special signal format.
Your computer cannot understand this signal directly.

What a Modem Does

• Converts ISP signal into digital data

• Converts digital data back into ISP signal

• Connects your home or office to the internet

Without a modem → no internet

Simple Example

1. Internet signal comes from ISP cable

2. Modem converts it

3. Now your router and devices can use it

Real-Life Analogy

Modem is like a language translator:

• ISP speaks “ISP language”

• Your network speaks “computer language”

• Modem translates between them

2. What Is a Router? (Traffic Controller)

Router = Decides where data should go

In your home or office, you have many devices:

• laptop

• mobile

• TV

• tablet

The router makes sure each device gets the correct data.

What a Router Does

• Gives local IP addresses to devices

• Sends internet data to the correct device

• Sends outgoing data to the internet

Simple Example

• You open YouTube on your phone

• Laptop opens Google

• Router sends YouTube data to phone

• Router sends Google data to laptop

Real-Life Analogy

Router is like a traffic police officer:

• You go left

• You go right

• You go straight

3. Hub vs Switch

Hub

Hub = Loudspeaker

• Receives data

• Sends it to all devices

• Every device hears everything

Example

Laptop sends a message
Hub sends it to:

• phone

• TV

• printer

Even if they don’t need it

Problems with Hub

• Slow

• Unsafe

• Creates network noise

Switch

Switch = Smart delivery system

• Sends data only to the correct device

• Uses MAC addresses

• Faster and more secure

Example

Laptop sends data to printer
Switch sends data only to the printer
Other devices don’t see it

4. What Is a Firewall? (Security Guard)

Firewall = Security gate

Firewall decides:

• who is allowed

• what traffic is blocked

What a Firewall Does

• Blocks hackers

• Allows trusted traffic

• Protects internal network

Simple Example

• Hacker tries to access a port

• Firewall blocks the request

• Website stays safe

Real-Life Analogy

Firewall is like a security guard:

• Valid ID? Enter

• No ID? Blocked

5. What Is a Load Balancer? (Traffic Distributor)

Load Balancer = Work distributor

When many users come at the same time:

• one server is not enough

Load balancer spreads traffic across servers.

What a Load Balancer Does

• Sends requests to multiple servers

• Prevents server overload

• Improves speed and reliability

Simple Example

10,000 users open a website:

• Some requests go to Server A

• Some to Server B

• Some to Server C

Real-Life Analogy

Like multiple toll booths on a highway:

• Cars are distributed

• No traffic jam

6. How All Devices Work Together (Real Example)

Opening a Website

User Device
   ↓
Router
   ↓
Modem
   ↓
Internet
   ↓
Firewall
   ↓
Load Balancer
   ↓
Switch
   ↓
Server

Step-by-Step Flow

1. You type a website URL

2. Router sends the request

3. Modem sends it to ISP

4. Internet carries it

5. Firewall checks security

6. Load balancer chooses a server

7. Switch delivers data to server

8. Response comes back to you

7. Why This Matters for Software Engineers ?

These devices directly affect:

• latency (speed)

• scaling

• security

• reliability

When deploying backend apps:

• Firewall protects APIs

• Load balancer handles traffic

• Network design affects performance