DNS FUNDAMENTALS

Networking Fundamentals

Learning Outcome

Topic Name-Recall(Slide3)

Before DNS, you learned:

• Every device on the internet has a unique IP address (like 192.168.1.1 or 8.8.8.8)
• IP addresses are how computers identify and communicate with each other
• These addresses act like a digital identity for each device on a network
• Data sent over the internet always includes a source IP (sender) and a destination IP (receiver)
• Devices use IP addresses to locate and deliver information accurately across networks
• Without IP addresses, computers wouldn’t know where to send or receive data
• However, IP addresses are not easy for humans to remember, especially at scale

Hook/Story/Analogy(Slide 4)

“Phone Contacts System”

Think of DNS like your phone contacts.

• You don’t remember phone numbers of everyone
• Instead, you save names like “Mom”, “Friend”
• When you call, your phone looks up the number behind the name

Similarly:

• Humans use domain names like google.com
• Computers use IP addresses like 142.250.183.14
• DNS acts like the contact list that maps names → numbers

Transition from Analogy to Technical Concept(Slide 5)

In the analogy:

• Contact name → Domain name
• Phone number → IP address
• Phone lookup → DNS resolution

Now, instead of a simple contact list in your phone, the internet uses a network of DNS servers to perform this lookup. When you enter a domain name, your system sends a request to these servers to find the corresponding IP address. This process happens within milliseconds, even though it involves multiple steps behind the scenes.

 So while the analogy is simple, in reality DNS is a distributed and hierarchical system that efficiently connects human-friendly names to machine-level addresses.

Core Concepts (Slide 6)

What is DNS?

DNS (Domain Name System) is the internet's phonebook. Computers communicate using IP addresses (numbers), but humans prefer names like google.com. DNS automatically translates domain names into IP addresses so your browser can find the right server. DNS (Domain Name System) is the system that converts human-friendly names (like google.com) into machine-friendly IP addresses (like 142.250.183.14).

How DNS Works (Domain → IP Resolution)

Here’s what happens when you type a URL:

• You type google.com in browser

• Your system asks a DNS Resolver:

  “Hey, what’s the IP for this?”

• Resolver checks cache (if already known)

Core Concepts (Slide 7)

• If not found, it goes on a journey:

  • Root Server → “Where is .com?”

  • TLD Server → “Where is google.com?”

  • Authoritative Server → “Here’s the IP”

• IP comes back → browser loads the website

Core Concepts (.....Slide N-3)

DNS Components

• DNS Components are the different parts of the Domain Name System that work together to convert a domain name (like google.com) into an IP address that computers can understand. The components are as follows:-
• Resolver (Your Assistant):-The DNS Resolver is the first point of contact that receives your request when you type a domain name. It checks its cache to see if it already knows the IP address to save time. If not, it starts querying other DNS servers on your behalf.
• Root Server (Top Boss):-The Root Server is the highest level in the DNS hierarchy and directs queries to the correct TLD server. It doesn’t store actual IP addresses for domains but knows where to find them. Think of it as a guide that points you in the right direction.

• TLD Server (.com, .org, etc.):-The TLD (Top-Level Domain) Server manages domain extensions like .com, .org, and .net. It helps narrow down the search by pointing to the authoritative server for the specific domain. It acts like a category filter in the DNS system

   

Core Concepts (.....Slide N-3)

• Authoritative Server (Final Authority):-The Authoritative DNS Server holds the actual DNS records, including the correct IP address of the domain. It provides the final answer to the resolver. This is the only server that gives the exact information needed to connect to the website.

Your Device  → Resolver  →   Root Server  →  TLD Server→  Authoritative Server  → IP Address

Core Concepts (.....Slide N-3)

Common DNS Record Types

DNS records are instructions stored on the authoritative server. Each record type answers a different question about the domain — where is the website, where do emails go, what is the IPv6 address, etc.  The Common records are as follows:-

A Record

An A (Address) Record maps a domain name to its IPv4 address, allowing browsers to locate the correct server. It is the most basic and commonly used DNS record. Without it, your domain wouldn’t know where to point.

AAAA Record:An AAAA Record maps a domain name to an IPv6 address, which is the newer version of IP addressing. It performs the same function as an A record but supports a much larger address space. It is essential for modern internet infrastructure.

Core Concepts (.....Slide N-3)

CNAME Record:A CNAME (Canonical Name) Record is used to create an alias for a domain, pointing it to another domain instead of an IP address. This helps manage multiple domain names easily without duplicating records. It’s commonly used for subdomains like www.

MX Record:An MX (Mail Exchange) Record specifies the mail servers responsible for receiving emails for a domain. It ensures emails are routed to the correct server instead of getting lost in the void. Without MX records, email communication wouldn’t work properly.

Example :-  

• A record — the main door number of a building. "google.com lives at number 142."
• AAAA record — same door, but the longer new address format used in newer buildings (IPv6 streets).

Core Concepts (.....Slide N-3)

Example :-  

• CNAME record — a nickname or alias. "Ask for 'The Smith Place' and staff will redirect you to 42 Baker Street." One address, many names.
• MX record — the mailbox address. Even if the office is at 42 Baker Street, all letters go to the post room at 10 Sorting Lane.

Summary

Which DNS server is the FIRST to receive your query when you type a domain name?

Which DNS server is the FIRST to receive your query when you type a domain name?

C. Authoritative Server

D. Recursive Resolver

If you visit the same website twice, why is the second DNS lookup faster?

If you visit the same website twice, why is the second DNS lookup faster?

C. The TLD server stores your IP

B. The resolver uses its cache

Which part of a URL defines how data is transferred?

Which part of a URL defines how data is transferred?

D. Query string

C. Protocol