Why DNS Exists

DNS (Domain Name System) translates human-friendly names like example.com into the IP addresses computers actually use to connect.

People remember names far better than numbers. DNS lets you type a website name instead of memorizing an address like 93.184.216.34, acting as the internet’s phone book.

Like a phone book maps a person’s name to a phone number, DNS maps a domain name to an IP address. You look up the name; DNS returns the number to dial.

Without it, you would need to know the exact IP of every site and service you use, which would be impossible to manage as addresses change.

A key benefit is flexibility. A website can move to a new server with a new IP address, but its domain name stays the same — only the DNS record is updated.

Users keep typing the same name and reach the new location automatically. This decoupling of name from address makes the internet far easier to operate.

DNS is not one giant directory but a distributed, hierarchical system spread across millions of servers worldwide. No single machine holds every record.

This distribution makes DNS scalable and resilient: responsibility for different parts of the namespace is delegated to different organizations.

Domain names are read right to left in a hierarchy. In www.example.com:

• .com is the top-level domain (TLD)
• example is the second-level domain
• www is a subdomain or host

An invisible root (.) sits above all TLDs at the top of the tree.

At the top sit the root servers, which know where to find the servers for each TLD. TLD servers (for .com, .org, country codes, etc.) know where each domain’s authoritative servers live.

This chain of delegation lets a lookup start at the top and drill down to the exact server holding the answer.

The authoritative name server holds the real, official records for a domain. Its answer is the definitive source of truth for that domain’s addresses.

When you register a domain, you point it at authoritative servers that store your records. Everything else in DNS exists to find and cache those authoritative answers.

A resolver (often run by your ISP or a public service) does the legwork of finding an answer on your behalf. Your device asks the resolver, which queries the hierarchy.

The resolver caches results so repeated lookups are fast. Your device only needs to know its resolver’s address to use the whole system.

The usual lookup is a forward lookup: name to IP address, the direction you use when browsing. DNS also supports a reverse lookup: IP address back to name.

Reverse lookups help with logging and email checks, where a server wants to confirm the name behind an address. Both directions rely on the same hierarchical system.

Because nearly every connection starts with a DNS lookup, DNS problems cause widespread, confusing outages. A site may be perfectly healthy, yet unreachable because its name will not resolve.

Technicians learn to suspect DNS early: if you can reach a site by IP but not by name, the fault is almost certainly DNS.

From browsing and email to app updates and cloud services, almost everything online depends on DNS first resolving a name. It runs quietly behind every click.

Understanding why DNS exists prepares you to follow a lookup step by step and recognize the record types and failures explored in the next lessons.

Confirm the purpose.

You learned why DNS exists.

• DNS maps human names to IP addresses — the internet’s phone book.
• It is distributed and hierarchical (root, TLD, authoritative servers).
• Names stay constant even when underlying IP addresses change.
• A resolver queries the hierarchy and caches answers for you.
• If IP works but the name fails, suspect DNS.