DNS (Domain Name System)

The Domain Name System (DNS) is a critical component of internet communication, translating human-readable domain names into IP addresses. This process enables users to access websites using easy-to-remember names instead of numerical IP addresses.

Key Points

• DNS Role: Translates domain names into IP addresses.
• Domain Names: Human-readable identifiers like www.cisco.com.
• IP Addresses: Numerical identifiers used by devices at Layer 3 of the OSI model.
• DNS Query: A message sent to a DNS server to resolve a domain name.
• DNS Records: Entries that map domain names to IP addresses and other information.
• DNS Hierarchy: A global structure of root servers, TLD servers, and authoritative servers.

Why DNS Exists

Computers use IP addresses for communication, but these addresses are hard for humans to remember. DNS maps easy-to-remember domain names to IP addresses, making internet navigation user-friendly.

DNS Resolution Process

1. Client Request: A user enters a domain name in a browser.
2. DNS Query: The system sends a DNS query to a DNS resolver.
3. Resolver Search: The resolver searches for the associated IP address.
4. Network Packet: Once resolved, the client builds network packets using the IP address.

Important: The IP header cannot contain domain names — only numerical IP addresses.

DNS Record Types

DNS uses structured messages for name resolution. Common record types include:

Record Type	Purpose	Example
A	Maps a name to an IPv4 address	example.com → 192.0.2.1
AAAA	Maps a name to an IPv6 address	example.com → 2001:db8::1
NS	Indicates authoritative DNS servers for a domain	Delegation info
MX	Specifies mail servers responsible for a domain	Email routing

DNS Hierarchy

DNS follows a strict hierarchical structure:

                [ Root DNS Servers ]
                        |
                [ TLD Servers (.com, .org, .fr) ]
                        |
             [ Authoritative DNS for domain ]
                        |
                     [ Client ]

1. Root Servers: Know where TLD servers are located.
2. TLD Servers: Manage domains like .com, .org, .fr, etc.
3. Authoritative Servers: Hold the actual records for a specific domain.

Example Flow

• Query root servers → “Who handles .com?”
• Query .com TLD servers → “Who handles cisco.com?”
• Query authoritative server → “What is the IP of www.cisco.com?”

Local DNS Cache

Operating systems store resolved entries locally to speed up future requests. On Windows, you can display cached DNS entries with:

ipconfig /displaydns

Manual DNS Queries

Tools like nslookup allow users to send DNS requests manually. Use cases include:

• Debugging DNS issues
• Checking server responses
• Testing different DNS resolvers

Diagrams / Explanatory Visuals

Simplified DNS Resolution Flow

User Browser
     |
     v
Local DNS Resolver
     |
     v
Root Server -> TLD Server -> Authoritative Server
     |
     v
IP Address returned
     |
     v
HTTP/HTTPS connection to Web Server

DNS Hierarchy Overview

Level	Role	Example
Root	Directs queries to TLD servers	.
TLD	Manages domain extensions	.com, .org, .fr
Authoritative	Holds actual domain records	dns.cisco.com

Common Beginner Mistakes

• DNS Definition: It means Domain Name System, not “Domain Name Service”.
• DNS Function: It resolves names to IP addresses; it does not deliver web content.
• Browser Communication: The browser must obtain an IP address before sending packets.
• AAAA Records: They represent IPv6 addresses, not “four A because of multiplication”.
• DNS Caching: Queries may be cached locally or by resolvers, affecting troubleshooting.

Practical Example

Home Network Scenario

1. You type www.wikipedia.org in your browser.
2. Your device asks a configured DNS resolver (often your ISP or a public DNS like 1.1.1.1).
3. The resolver contacts root, TLD, and authoritative servers.
4. The IP address is returned.
5. Your computer opens a TCP connection to that IP on port 443 (HTTPS).

Key Takeaways

• DNS translates domain names into IP addresses.
• It operates mainly at the application layer but enables Layer-3 communication.
• DNS is distributed and hierarchical (root → TLD → authoritative).
• Common records: A, AAAA, NS, MX.
• Systems cache DNS results to speed up future requests.
• Tools like nslookup allow manual DNS queries.
• Without DNS, users would need to memorize IP addresses.

Learn More

• RFC 1034: Domain Names: Concepts and Facilities (IETF)
• RFC 1035: Domain Names: Implementation and Specification (IETF)
• Cloudflare Learning Center: DNS Fundamentals
• Cisco Networking Academy: DNS Concepts
• IANA Root Zone Database
• IEEE & OSI Model Documentation