How do you tell CSS exactly which part of the page you want to change?

You might want one paragraph to be big and blue, but another paragraph to be small and gray. How does the browser know the difference?

This is where CSS Selectors come in. If HTML is the raw material and CSS are the styling instructions, then Selectors are the bridge between them. They are the foundation of CSS; without them, you cannot style anything.

In this guide, we will break down the essential ways to target your elements.

The "Crowded Room" Analogy

To understand how selectors work, let's imagine your HTML document is a crowded banquet hall filled with hundreds of people (elements). You are standing on a stage with a microphone (the CSS file), and you need to give instructions to specific people.

How you address them determines who listens.

1. Broad: If you shout, "Hey, human!" everyone in the room will look up. It’s too broad.

2. Specific Group: If you shout, "Everyone wearing a red shirt, stand up!" only a specific group will respond.

3. Unique Individual: If you shout, "John Smith at Table 9, come to the stage!" only one very specific person will move.

CSS selectors work exactly the same way. Let’s look at the three core selectors in that order.

The Core Selectors

1. The Element Selector (The Broad Shout)

This is the simplest selector. It targets every single instance of an HTML tag on your page.

• Analogy: "Hey, human!"

• When to use it: Setting site-wide defaults, like the base font size for all paragraphs or removing default margins from the page body.

How it works: You just write the name of the HTML tag without brackets.

HTML:

<p>This is paragraph one.</p>
<p>This is paragraph two.</p>

p {
  color: darkblue;
  font-size: 18px;
}

Result: Both paragraphs on the page turn dark blue and become 18px size.

2. The Class Selector (The Specific Group)

The Element selector is often too blunt. What if you want most paragraphs to be plain, but you want a specific few to look like "warning" notes?

You use a Class. Classes are attributes you add to your HTML to categorize elements. You can use the same class name on as many elements as you want.

• Analogy: "Everyone wearing a red shirt."

• Syntax: In CSS, a class selector always starts with a dot (.).

HTML:

<p>This is a normal paragraph.</p>
<p class="warning-text">Be careful! This is important.</p>
<p>Another normal paragraph.</p>
<p class="warning-text">Don't forget to save your work.</p>

CSS:

.warning-text {
  color: red;
  font-weight: bold;
}

Result: The first and third paragraphs remain plain. The second and fourth become bold and red.

Pro Tip: Classes are your best friend in CSS. Because they are reusable, they are the most common way to style web pages

3. The ID Selector (The Unique Individual)

Sometimes, there is an element on your page that is totally unique. There is only one of it. Think of your main website logo, or the main navigation header container.

For these, we use an ID.

• Analogy: "John Smith at Table 9."

• The Golden Rule: An ID name must only be used once per page.

• Syntax: In CSS, an ID selector always starts with a hash/pound sign (#).

HTML:

<div id="main-header">
  <h1>My Website</h1>
</div>

CSS:

#main-header {
  background-color: #333; /* Dark gray background */
  color: white;
  padding: 20px;
}

Wait, shouldn't I just use a class? Many modern developers prefer using classes even for unique elements just to keep things consistent. However, IDs are still useful, particularly if you need to target an element with JavaScript later. For styling, use IDs sparingly.

Working Smarter: Combining Selectors

Once you master the big three, you can start combining them to write cleaner code.

Group Selectors (Don't Repeat Yourself)

Imagine you want your <h1>, <h2>, and paragraphs to all share the same font family. You could write three separate rules, but that's repetitive. Instead, group them using commas.

CSS:

h1, h2, p {
  font-family: Helvetica, Arial, sans-serif;
  color: #444;
}

Descendant Selectors (Context Matters)

Sometimes you only want to style an element if it's inside another specific element.

Let's say you want all links (<a> tags) on your site to be blue. Except if the link is inside your dark footer—then you want it to be white so it's readable.

You use a space between selectors to indicate "inside of."

HTML:

<p>Visit our <a href="#">contact page</a>.</p>

<footer id="site-footer">
    <p>Copyright 2023. <a href="#">Privacy Policy</a></p>
</footer>

CSS:

a {
  color: blue;
}

/* Rule 2: Links INSIDE the footer id */
#site-footer a {
  color: white;
}

Who Wins? A Very High-Level Look at Priority

What happens if you have conflicting instructions?

Imagine your CSS has these two rules:

1. An Element selector says all paragraphs (p) should be Gray.

2. A Class selector says paragraphs with the class .special should be Red.

If you have <p class="special">Hello</p>, what color will it be?

It will be Red.

The browser follows a hierarchy of "Specificity." The more specific the selector, the more weight it carries.

• Lowest Priority: Element selector (The broad shout to "humans")

• Medium Priority: Class selector (The group wearing "red shirts")

• Highest Priority: ID selector (The specific "John Smith")

The browser always listens to the most specific instruction it can find for an element.

Summary

CSS selectors are how you tell the browser what to style. You can't build a website without them.

• Start broad with Element selectors for defaults.

• Use Class selectors for most of your styling needs (reusable groups).

• Use ID selectors rarely for unique structural elements.

• Remember that more specific selectors override broader ones.

Mastering these basics is the first giant step toward making your websites look exactly the way you pictured them.

Without HTML, the web would just be a blob of unformatted text.

What is an HTML Tag?

Think of an HTML tag like a storage box.

• You have an opening tag (opening the box).

• You put content inside (the stuff in the box).

• You have a closing tag (taping the box shut).

Tags are keywords surrounded by angle brackets, like <tagname>. They tell the browser how to display the content inside them.

The Anatomy of a Tag

Here is the standard syntax:

<p>This is a paragraph.</p>

• Opening Tag: <p> (Starts the paragraph)

• Content: This is a paragraph. (The text you see on the screen)

• Closing Tag: </p> (Ends the paragraph—notice the forward slash /)

Tags vs. Elements: What's the Difference?

New developers often use these terms interchangeably, but there is a distinct difference.

• Tag: The code bits in the brackets (e.g., <h1> or </h1>).

• Element: The entire package, from the opening tag to the closing tag, including the content inside.

Formula: Opening Tag + Content + Closing Tag = HTML Element

Visualizing the Breakdown

Element
┌──────────────────────────────┐
<button> Click Me </button>
└─┬────┘ └──┬───┘ └───┬─────┘
Opening   Content   Closing
  Tag                 Tag

Self-Closing (Void) Elements

Some elements don't hold content. Since they don't have "stuff" inside them, they don't need a closing tag. These are called self-closing or void elements.

Common examples:

• <br>: Inserts a line break.

• <img>: Embeds an image.

• <hr>: Creates a horizontal line.

Block-Level vs. Inline Elements

Understanding how elements sit on the page is crucial for layout.

1. Block-Level Elements

These are the "greedy" elements. They always start on a new line and take up the full width available (like a block stretching from left to right).

• Examples: <div>, <h1>, <p>, <ul>

• Visual: Imagine stacking cardboard boxes vertically on top of each other.

2. Inline Elements

These are the "social" elements. They do not start on a new line; they only take up as much width as necessary and sit happily next to other elements.

• Examples: <span>, <a> (links), <b> (bold)

• Visual: Like words in a sentence flow from left to right.

Analogy:

• Block elements are like houses on a street (each takes up a specific plot of land).

• Inline elements are like furniture inside the house (they sit next to each other within the space).

Commonly Used Tags

Here are the essentials you will use 90% of the time:

What is browser :

A browser is simply software that lets you access, view, and interact with websites on the Internet. what browser does?

What browser does ?

• It fetches data from web servers when you enter a URL

• it downloads files such as HTML, images, text, video, etc., using protocols like HTTP/HTTPS.

• it parser those files and render it on display .

• it lets client to navigate in web page

Main parts of Browser :

1. UI (User Interface) : Ye woh parts hain jinke saath user interact karta hai. like tabs , address bars, navigation bar, bookmark bar, menu, settings etc.

2. Browser Engine: UI aur rendering engine ke beech bridge ka kaam karta hai. Decide karta hai kab, kaise page load hoga.

3. Rendering Engine : Ye engine code ko webpage me convert karta hai.

4. javascript engine: Website ka logic & interactivity yahin run hoti hai.

5. Networking layer: Internet se baat karne ka kaam karta hai.

6. Disk api : Browser locally data store karta hai for speed & convenience.

Networking: how a browser fetches HTML, CSS, JS

For now I will explain this in diagrammatic matter . read that image carefully to understand how browser works.

DOM & CSSOM creation:

Dom is created while parsing HTML files and CSSOM is created while parsing CSS files. both works together while rendering inside browser. This 2 DOM and CSSOM meets inside render tree where their workflow is designed . after render tree the final frame is get constructed and then reflow and painting occurs then then the website is get displayed to user.

Thank you for reading . Have a happy learning journey. I hope this article added some value for your given precious time.

Version control exists to address several issues related to managing changes in files and projects, and one of the classic examples illustrating the need for version control is the "Pendrive Problem." This problem arises when multiple versions of a file are saved on different devices, such as USB drives (pendrives), leading to confusion and potential data loss.

The Pendrive Problem typically involves scenarios where:

1. Multiple Copies: Users create multiple copies of the same file on different pendrives or devices, making it difficult to track which version is the most recent or accurate.

2. Collaboration Issues: When multiple people work on the same project, they might each have their own version of the files on separate pendrives, leading to conflicts and difficulties in merging changes.

3. Data Loss: Without a centralized system to manage changes, important updates might be overwritten or lost if the wrong version is used or if a pendrive is misplaced.

4. Lack of History: Without version control, there is no easy way to view the history of changes, making it challenging to revert to previous versions if needed.

Version control systems, like Git, solve these problems by providing a centralized repository where all changes are tracked, allowing for easy collaboration, version tracking, and recovery of previous file states. This ensures that everyone is working on the most up-to-date version and that changes are systematically managed.

Understanding Git: The Inner Workings and Importance of the .git Folder

Definition of Git

Git is a distributed version control system designed to handle everything from small to very large projects with speed and efficiency. It allows multiple developers to work on a project simultaneously without interfering with each other's changes. Git tracks changes in the source code, enabling developers to collaborate and maintain a complete history of modifications, which can be used to revert to previous versions if necessary.

Overview of the .git folder

The .git folder is a crucial component of a Git repository, acting as the database where all the metadata and object data for the project are stored. It contains all the information necessary for version control, including configurations, references to branches and tags, and the history of commits. The .git folder is typically located in the root directory of a Git repository and is hidden by default. Understanding the structure and contents of the .git folder is essential for managing and troubleshooting a Git repository effectively.

Importance of understanding the .git folder

Understanding the .git folder is important because it is the backbone of a Git repository, containing all the data necessary for version control. By comprehending its structure and contents, developers can effectively manage and troubleshoot repositories. This knowledge helps in maintaining the integrity of the repository, resolving issues like corrupted data, and understanding how Git tracks changes. It also aids in performing advanced operations, such as manual recovery of lost commits, and ensures better collaboration and project management.

Why Git is used ?

In simple words we can refer git as a program that can track user code. It can track changes made by user in his code . It can tell when and where the change has been made by the user.In programming, multiple people can work on the same project. It is hard to track each person's code and then merge it into a single source of truth (which is the main project). Git is used to merge code from different people, track changes, and see who is working on the code.

Git Basics and Core Terminologies

1. Repository (Repo): A storage location for your project, which includes all files and the history of changes made to them.

2. Commit: A snapshot of changes made to the files in the repository. Each commit has a unique ID and records who made the changes and when.

3. Branch: A separate line of development within a repository. Branches allow multiple people to work on different features or fixes simultaneously.

4. Merge: The process of combining changes from different branches into a single branch.

Common Git Commands

1. git init: Initializes a new Git repository in the current directory.

2. git add [file]: Stages changes in the specified file for the next commit.

3. git commit -m "[message]": Records the staged changes with a descriptive message.

4. git status: Displays the state of the working directory and staging area.

5. git log: This command shows the commit history for the repository. It lists all the commits made in the repository, along with details such as the commit ID, author, date, and commit message. It's helpful for reviewing the project's history and understanding the sequence of changes

6. git revert: This command creates a new commit that undoes the changes made by a previous commit. Unlike git reset, which can alter the commit history, git revert maintains the history by adding a new commit that reverses the specified changes. It's useful for safely undoing changes in a collaborative environment.

example

why internet needs this protocols ?

imagine internet as a massive highway . IP is that system which guides cars (data packets ) to move from one computer to another. IP is very basic system it just dumps the data to another computer and does not care about the data is reached or crashed or being theft. That is why we need Transport layer protocols to handles what happens after the data reaches the device. Without them the internet would be chaotic.

What is TCP?

Transmission Control Protocol (TCP) is a transport layer protocol , It is a standard that defines how to establish and maintain a network conversation through which application program exchanges data. if IP is a address system then TCP is a guarantee delivery service.

How TCP works?

Assume when we call someone from phone,

• we dial the number and say hello that is ( request connection )

• then other person will say hello ( that’s acknowledge request)

• you starts talking ( connection established)

That was a real life scenario how does 3 way handshake connection establishes. but now lets talk about how TCP do this, the process known as 3 way handshake :

Key Features of TCP:

1. Reliability : very time TCP sends a packet, it starts a timer. If the receiver doesn't send back an acknowledgment (ACK) saying "I got it" before the timer runs out, TCP assumes the packet was lost and resends it automatically.

2. Order / Sequence : Data packets often take different routes across the internet and arrive out of order (e.g., Packet 3 arrives before Packet 2).TCP numbers every packet. The receiver uses these numbers to put them back in the correct order before handing the data to the app.

3. Flow control : TCP manages the speed of data. If the receiver is overwhelmed, it tells the sender to slow down.

4. Error checking : If the data is bad, TCP discards it and asks for a fresh copy.

When is TCP used :

TCP is used in any application where accuracy is more important than speed. for example

1. web browsing ( we don’t want website showing incomplete texts )

2. emails

3. file transfer

4. Text messaging apps like WhatsApp

real world example for TCP are :

• open a website

• Log in to an account

• Send an email

What is UDP ?

User Datagram Protocol (UDP) is a transport layer protocol which is used to send data quickly. There is no confirmation weather data reached or not , is is just like throwing data to IP address and we hope that it arrives , UDP does not wait for confirmation and instantly send other data. there is no 3 way handshake process in this protocol.

How does UDP works :

unlike TCP here there is no 3 way handshake connection , it simply just takes application data into small packets and attaches a very small header just to know where data is going and then it just sends data super quick.

Features of UDP:

1. Unreliable : UDP is often called a "Best Effort" service. If a packet drops due to network congestion, UDP does not resend it. The data is simply lost forever.

2. unordered : If you send Packet A, then Packet B, they might arrive as B then A.

3. Lightweight and high speed

4. no control flow

When is UDP used :

• Online gaming

• video streaming

• DNS

real life scenario of UDP is video streaming platform like Netflix , jiohotstar, games etc .

Difference between TCP & UDP :

What is HTTP:

HTTP stands for HyperText Transfer Protocol. if TCP is delivery truck then HTTP is the order of delivering the packets . it defines the format and language that browsers and server talk to each other.

for eg: when we search google.com

1. HTTP creates a specific message: "GET me the homepage."

2. it hands this message to TCP to deliver it safely.

3. The Server's TCP receives it and hands it to the Server's HTTP

4. Server understands the message and sends back the website code (HTML).

Where does it fits :

• application layer

• transport layer

• network layer

• physical layer : actual wifi radio waves or ethernet cables.

Relationship between TCP and HTTP :

HTTP has almost exclusively used TCP. When you load a webpage, you need the HTML, CSS, and JavaScript to arrive perfectly. If a line of JavaScript is missing (packet loss), the button on the site won't work. Therefore, HTTP relies on TCP's reliability.

Thank you for reading . Have a happy learning journey. I hope this article added some value for your given precious time.

How Server works ?

Server is a powerful computer that has 3 main job to do which is

to store data

to process requests

to send response to client

Server is a computer which works 24×7 hours , which is always connected to internet and which handles thousands or sometimes millions of clients.

while using our computer we talk to server many times and we didn’t even notice that thing. when and how we talk to server

• opening a website

• login into app

• watch a video

• send a message

• save something

Our computer cannot do everything by itself. Consider our device as a client and server as a remote powerful computer.

How do Clients talk to servers ?

The clients talk to server by using some protocols HTTP/HTTPS , Request and responses and APIs. Every request will be looks like this:

Now the big question arise is how does this requests goes to the server ? do developers send all requests manually ? So the answer is NO , developer doesn’t send requests manually . This is where cURL comes in.

What is cURL ?

cURL means client URL . It is a command line tool that is used to

• fetch data from URL

• send request to server

• test APIs

• to debug backend services

Why we need cURL ?

cURL is a way to talk with servers without browser. Because browser hides details such as IP,NS servers, etc , browsers can automates all things and are not good for testing APIs. So cURL is used we need it because:

• fetch data from URL

• check server response

• sends GET,POST,PUT,DELETE requests

• inspect header ,status codes , errors

Sending Request using cURL:

The simplest possible way to fetch a website is

curl http://chaicode.com

it sends an HTTP GET request , downloads the HTML on webpage and prints it out in our terminal.

Understanding Request and Response:

After using that command curl http://chaicode.com cURL generates a request. A request has basically 4 parts;

1. method => GET

2. path => /

3. headers => database

4. body => to get response for GET

servers receives the request and gives a HTTP Response in the body. Response also has 3 parts :

1. status code

2. Headers

3. Body

How cURL talks to APIs:

API is just a server endpoint that listens for HTTP requests , expects specific methods, body and gives response. cURL is a client that sends those requests exactly as API expects.

Common mistakes beginners make with cURL:

1. forgetting the HTTP method

2. not setting content type

3. wrong quotes (in JSON)

4. forgetting Authentication Header

5. not checking status code

6. ignoring error messages

7. forgetting -v while debugging

8. expecting cURL to behave like a browser

9. copy pasting without understanding

Thank you for reading . Have a happy learning journey. I hope this article added some value for your given precious time.

There are different roles of many network devices for providing internet to our home, offices, mobile phones. Let’s have a detailed discussion on them .

What is Modem ?

Modem is a device that connects our local network with ISPs by converting ISP signals into data that our device can understand.

Why do we need modem ?

Data transferred from ISP is in the form of signals that can be a light signal(fiber) , electrical signals (copper wires), or may be a radio signal (wireless). Our computer device only understands binary that is 0 & 1 they can’t understand this signals.

So modem acts as a translator between our devices and ISP signals . It translates ISP signals into binary form so that our devices can understand it.

What is Router ?

A router is a networking device that connects our local network to other networks (including internet) and decides where data packets should go. If modem brings the internet then router decides where should internet go. It connects 2 different networks WAN (internet/ISP side) and LAN(our local network). That is why it is called router it routes traffic between 2 network.

Why do we need a Router ?

Router enables us to use one Internet connection in many devices securely and efficiently. Without router there should be no WiFi , no security layer , only one device can use internet but because of router now many device can access the same internet connection.

Difference between Modem and Router :

Switch vs Hub :

What is hub?

Hub is a simple networking device that broadcast data to all connecting devices. In current era Hub is a dumb and old device because it just broadcasts all the data so there is no security, anyone can hear what data is sending to whom.

For eg

What is SWITCH ?

A Switch is an intelligent LAN device that sends data only to the intended device( where user wants data to go). Switch actually knows who is connected and where is connected.

Difference between HUB & SWITCH:

FIREBALL the security guards :

If routers are the brain of computer then fireball are security guards. Fireball is the security device or software that monitors , filters, and control network traffic based on predefined protocols. In short fireball allows what is allowed and what is it be blocked.

Why “Security Lives Here”?

Every data packet entering or leaving the network must have passes through fireball. Fireball checks it according to security protocols and takes decision to allow it entering into network or blocked that data pack. Without fireball there would be no control into the network and it would become an open network which is very risky. Fireball are mostly built-in routers or often come as a separate device.

Importance of Load Balancer in real systems:

A load balancer is a system that distributes incoming traffic across multiple servers so that no single server gets overloaded. Sometime when there are so many users actively working on a site then the site crashes due to overload or sometime when servers are down then also site crashes . To overcome this situation we use load balancers. So that it distributes the traffic and releases load from the server.

All These Network Devices Work Together (Real-World Setup)

Internet signals coming from ISP’s entered into out networking system from modem. Then it is controlled by router and fireball. It travels inside LAN via switches and finally it is being scaled using load balancers.

Thank you for reading . Have a happy learning journey. I hope this article added some value for your given precious time.

Why do we need DNS Record Types

DNS records are the information stored in DNS which shows

• Where the website is located

• Where the emails would go

• Who manages the domain

Suppose we open a company name it as “SONI Pvt Ltd” . DNS records will be like for diffrent departments of our company.

Why each DNS is needed

1. A/ AAAA record

   It opens the website of the company. Without it we can’t open the website of our company.

2. MX record

   Without it emails cannot be reached to our company

3. CNAME record

   Without CNAME we can’t have alliance like www.soni.com we can’t use www. Or we can we that without CNAME www and non-www cannot work together.

4. NS record

   NS is the domain controller. Without NS the domain is dead and no record of our domain will be found.

5. TXT record

Used for Email security, Domain ownership verification, security policy . Without TXT record all the emails will go to spam and DNS services like hostinger, godaddy can’t be able to verify our domain.

DNS Record Types explained in detail:

A / AAAA Records

A records maps a domain to IPv4 address. What is IPv4? It is basically an Internet Protocol Version 4. It is a foundational system that assign unique 32bits numerical address like 132.21.22… to devices enabling them to communicate over the internet by routing data packets across networks. though its limited address pool (around 4.3 billion) led to the development of IPv6 to handle the growing number of connected devices. And that’s how AAAA got introduced. They maps domain to IPv6 address. But AAAA have 128 bits of numerical address.

Here the role of A / AAAA records is to connect the domain lets say Chaicode.com and its unique IPv4 address lets say 13.12.1 together.

CNAME Records:

CNAME means canonical name. Cname makes one domain name an alias of other. Unlike A/ AAAA record it does not points to a IP address but it always point to another Domain name.

For eg. www.chaicode.com and Chaicode.com are 2 different names but using CNAME we can redirect the user to our original website i.e Chaicode.com also they both will have same IP address bcoz of CNAME.

CNAME avoids duplication of websites .

chaicode.com A 203.0.113.25

www.chaicode.com CNAME chaicode.com

NS records:

NS records tells the browser that which DNS server are authoritative for our domain.

chaicode.com NS ns1.cloudflare.com chaicode.com NS ns2.cloudflare.com

NS records are stored at TLD server. We can check the NS by using “dig chaicode.com NS” in our terminal.What happens when you change NS?

Changing NS means:

• You switch DNS provider

• Old DNS stops working

• New DNS becomes source of truth

⚠️ DNS propagation may take time (TTL).

MX Record:

MX means mail exchange record. It tells the browser that where the mails for our domain should deliver. For eg hello@chaicode.com

TXT Records:

TXT (Text) records store human readable instructions and proofs for a domain.
They’re mainly used for email security, domain verification, and policies.

Why TXT records exist?

DNS can’t just route traffic, it also needs to answer questions like:

• “Is this server allowed to send email for this domain?”

• “Does this domain really belong to you?”

• “How should email receivers treat suspicious mail?”

TXT records are where these answers live.

Types of TXT records:

1. SPF : it tells who is allowed to send emails at chaicode.com

2. DKIM: In this Emails are cryptographically signed. Receivers can verify authenticity.

3. DMARC: what to do if both SPF and DKIM fails ? Here comes the role of DMARC. If an email fails checks → quarantine it and send reports to Chaicode

4. Domain verification : to check that is domain is under control or not.

   

How all DNS records work together for the same website?

Remember all DNS records dont do the same job. they all have different roles. Lets break it down to understand clearly.

• NS Record: tells that who manages the domain.

• A/AAAA Record : locates the Website and give IP address to browser

• CNAME Record: creates the alias like www.chaicode.com

• MX Record: Check where emails are going

• TXT record: checks weather the email is trusted / domain verified.

Each record has a strict role todo that is why they dont clash with each other and works together for the same website. Website needs multiple DNS records to function properly.

Thank you for reading . Have a happy learning journey. I hope this article added some value for your given precious time.

Before starting to our name resolution topic let me clear some basic terminology’s such as DNS and DNS resolution are 2 different things . They often used interchangeably in casual conversation, but they are different aspects of technology.

How are they differ from each other

DNS (Domain Name System) : This is an entire system or Infrastructure itself. It is a global database that stores records and maps domain names to IP addresses. We can say it as a “Phonebook” of internet. For eg. Hostinger, GoDaddy, Versel etc.

DNS Resolution : This is an active process or action of using that system to find answers. It is a multiple step process. Starting from user request through various servers like Root,TLD and Authorotative servers to resolve user request.

Overview

In this blog we will understand how this process of DNS Resolution works in detailed and simple way. Along with that we will understand about Dig and Dig commands.

How DNS Resolution works

Here are some simple steps how this whole process works.

1. First the user requests the browser to open Chaicode.com in his browser. The browser searches for the domain in its cache if its not available there then It will take his request to .com domains list or we can say into Recursive DNS.

2. The recursive DNS will now search for the domain in its cache if its not there then it will redirect the request to Root Server

3. The Root server will now tell the recursive DNS to go to this specific TLD(Top Level Domain) server that manages information for specific domain like .com , .org , .gov etc.

4. Now the Recursive DNS will go to the specific TLD server and will ask for chaicode.com .

5. The TLD server will provide us the NS(name server)

6. The Recursive DNS will go to the Authoritative DNS server to get the IP address for our website

7. Authoritative DNS will give IP address like 143.11.12.1 to our recursive DNS

8. Then it gives IP address to browser so that the user can get access for the Web site he wants.

Unleashing the Curiosity

Ever wondered what if we can get the record of IP address also the name server of the website directly into our computer. Yes, we can do that thing using DIG (Domain Information Groper). We just simply type the command dig chaicode.com in terminal or warp then it will directly tell us the IP address and DNS details for that website.

How dig works and what is role of DIG !

DIG is a query tool that asks DNS servers about how a domain name get resolved to a IP address.

Some useful DIG commands

1. DIG.NS

   NS is a DNS record type. It indicates which server are responsible for the domain names. It show us the Authoritative server

2. dig com NS

   This shows DIG which is a query tool, .com which is a TLD and NS asks for name for that TLD where .com is available. It returns the TLD servers where .com is located.

3. Dig google.com NS

   It finds the name server which are authoritative for the domain google.com it returns something like.

   google.com. NS ns1.google.com.

   google.com. NS ns2.google.com.

   google.com. NS ns3.google.com.

4. Dig google.com

   It asks DNS about the IP address of google.com also asks for the record type of the domain and its authoritative server . It also returns TTL seconds to reach the server. The output will look something like this. google.com. 300 IN A 142.250.182.14

   300 → TTL (seconds)

   A → IPv4 record

   142.250.182.14 → IP address

That’s it . Thank you for reading . Hope you understand the concepts well.