Lesson 06 — Domain Name System (DNS)

Lesson Overview

Imagine trying to remember the IP address of every website you visit.

Instead of typing:

https://www.google.com

You would need to remember something like:

142.250.183.206

Now imagine remembering the IP addresses for hundreds of websites, cloud applications, APIs, and enterprise systems.

That would be nearly impossible.

This is where the Domain Name System (DNS) comes in.

DNS acts as the Internet’s phonebook, converting easy-to-remember domain names into IP addresses that computers use to communicate.

Every website, cloud platform, email system, and enterprise application depends on DNS.

Understanding DNS is essential for Cloud Engineers, Network Engineers, Cybersecurity Professionals, DevOps Engineers, and Solutions Architects.

Learning Objectives

After completing this lesson, you will be able to:

Explain what DNS is.
Understand why DNS is important.
Learn how DNS name resolution works.
Identify common DNS record types.
Understand DNS in cloud environments.
Troubleshoot common DNS issues.

What is DNS?

The Domain Name System (DNS) is a distributed naming system that translates domain names into IP addresses.

For example:

www.gohackerscloud.com

↓

DNS

↓

203.0.113.15

Humans remember names.

Computers communicate using IP addresses.

DNS connects the two.

Why DNS Matters

Without DNS:

Websites could not be accessed using names.
Email delivery would fail.
Cloud applications would be difficult to use.
APIs could not easily communicate.
Users would need to memorize IP addresses.

DNS makes the Internet user-friendly and scalable.

How DNS Works

Suppose you open:

https://www.gohackerscloud.com

The following process occurs:

User

↓

Web Browser

↓

DNS Resolver

↓

Root DNS Server

↓

Top-Level Domain (TLD) Server

↓

Authoritative DNS Server

↓

IP Address Returned

↓

Browser Connects to Web Server

This process usually completes in just a few milliseconds.

Step-by-Step DNS Resolution

Step 1

The user enters a domain name.

www.gohackerscloud.com

Step 2

The browser checks its local DNS cache.

If found, the process ends immediately.

If not…

↓

Step 3

The request is sent to the configured DNS Resolver.

Examples:

ISP DNS
Google DNS
Cloudflare DNS
Enterprise DNS Server

Step 4

If the resolver doesn’t know the answer, it queries the Root DNS Server.

Step 5

The Root Server directs the resolver to the correct Top-Level Domain (TLD).

Example:

.com
.org
.net
.edu

Step 6

The TLD server points to the domain’s Authoritative DNS Server.

Step 7

The Authoritative DNS Server returns the correct IP address.

Example:

203.0.113.15

Step 8

The browser connects to the destination web server.

The website loads successfully.

DNS Resolution Diagram

User

↓

Browser

↓

DNS Resolver

↓

Root DNS

↓

TLD DNS

↓

Authoritative DNS

↓

IP Address

↓

Website

This process happens every time you visit a new website.

DNS Components

DNS Client

The device requesting the DNS lookup.

Examples:

Laptop
Mobile Phone
Server

DNS Resolver

Receives DNS queries from clients and performs lookups.

Examples:

Google DNS
Cloudflare DNS
ISP DNS

Root Name Server

The first level of the global DNS hierarchy.

There are 13 logical Root Server systems distributed globally.

Top-Level Domain (TLD) Server

Responsible for domains such as:

.com
.org
.net
.gov
.edu

Authoritative Name Server

Stores the official DNS records for a domain.

Only the authoritative server can provide the definitive answer for that domain.

Common DNS Record Types

DNS stores different types of records.

A Record

Maps a domain name to an IPv4 address.

Example:

www.gohackerscloud.com

↓

203.0.113.15

AAAA Record

Maps a domain to an IPv6 address.

CNAME Record

Creates an alias for another domain.

Example:

learn.gohackerscloud.com

↓

courses.gohackerscloud.org

MX Record

Specifies the mail server responsible for receiving email.

Example:

mail.gohackerscloud.com

TXT Record

Stores text information.

Common uses:

SPF
DKIM
Domain Verification
DMARC

TXT records are widely used for email security and domain ownership verification.

NS Record

Identifies the authoritative name servers for a domain.

Public DNS Servers

Many organizations use public DNS services.

Provider	DNS Server
Google	8.8.8.8 / 8.8.4.4
Cloudflare	1.1.1.1 / 1.0.0.1
Quad9	9.9.9.9
OpenDNS	208.67.222.222

These services provide fast and reliable DNS resolution.

DNS Caching

To improve performance, DNS responses are cached.

Caching occurs on:

Web Browsers
Operating Systems
DNS Resolvers
Enterprise DNS Servers

Benefits include:

Faster browsing
Reduced Internet traffic
Lower latency
Improved performance

DNS in Cloud Computing

Cloud platforms provide managed DNS services.

Examples:

Cloud Provider	DNS Service
AWS	Amazon Route 53
Microsoft Azure	Azure DNS
Google Cloud	Cloud DNS

These services provide:

High availability
Global redundancy
Automatic scaling
Low latency
Health checks

Cloud Engineers use these services to manage public and private domains.

DNS in Enterprise Networks

Organizations use DNS for:

Internal applications
Active Directory
Email services
Database servers
File servers
VPN services
Cloud resources

Without DNS, enterprise networks become difficult to manage.

DNS in Cybersecurity

Attackers often target DNS because it is critical to network communication.

Common threats include:

DNS Spoofing
DNS Cache Poisoning
DNS Tunneling
DNS Amplification Attacks
Domain Hijacking

Security teams protect DNS by implementing:

DNSSEC
DNS Monitoring
Threat Intelligence
Secure DNS Resolvers
Logging and Auditing

Common DNS Commands

Windows

nslookup www.gohackerscloud.com

ipconfig /displaydns

ipconfig /flushdns

Linux

dig www.gohackerscloud.com

host www.gohackerscloud.com

nslookup www.gohackerscloud.com

These commands help troubleshoot DNS issues.

Real-World Example

Suppose a student visits:

https://learn.gohackerscloud.com

The communication process is:

Browser

↓

DNS Resolver

↓

Amazon Route 53

↓

Cloud Load Balancer

↓

Application Server

↓

Student Dashboard

Without DNS, the browser would never know where to send the request.

Best Practices

As an IT professional:

Understand how DNS resolution works.
Use reliable DNS providers.
Monitor DNS performance.
Protect DNS infrastructure.
Document DNS records.
Remove unused records.
Enable DNS logging.
Secure domains using DNSSEC where appropriate.

Reliable DNS is essential for business continuity.

Key Takeaways

After completing this lesson, you should understand:

What DNS is.
Why DNS is important.
The DNS resolution process.
Common DNS record types.
DNS services in cloud platforms.
DNS security fundamentals.

Summary

DNS is one of the most important services on the Internet.

It enables users to access websites and applications using easy-to-remember names while allowing computers to communicate using IP addresses.

Whether you’re deploying applications in AWS, securing enterprise infrastructure, configuring Kubernetes services, or troubleshooting network issues, DNS will be one of the most frequently used technologies in your IT career.

Mastering DNS fundamentals is an essential step toward becoming a skilled Cloud Engineer, Network Engineer, or Cybersecurity Professional.

Next Lesson

➡️ Lesson 07 — Dynamic Host Configuration Protocol (DHCP)

In the next lesson, you’ll learn how devices automatically receive IP addresses, understand the DHCP lease process, and discover why DHCP is essential for managing modern enterprise and cloud networks.