Skip to main content
DNS Explained – Complete Beginner to Advanced Guide
CHAPTER 02 Beginner

History and Evolution of DNS

Updated: May 15, 2026
15 min read

# CHAPTER 2

History and Evolution of DNS

1. Introduction

The Domain Name System was not present when the internet was first born. In fact, for the first decade of network engineering, the internet relied on a completely manual, hilariously inefficient method to keep track of computers. Understanding *why* DNS was created requires understanding the breaking point of the early internet. In this chapter, we will travel back to the ARPANET days of the 1970s, explore the legendary HOSTS.TXT file, and uncover how Paul Mockapetris engineered a distributed, hierarchical system that successfully scaled to handle billions of modern devices.

2. Learning Objectives

By the end of this chapter, you will be able to:
  • Describe how early computer networks mapped names to IP addresses.
  • Explain the function and limitations of the HOSTS.TXT file.
  • Understand the historical breaking point that necessitated the invention of DNS.
  • Recognize Paul Mockapetris's contribution to modern networking.
  • Contrast early centralized networking with modern decentralized infrastructure.

3. Beginner-friendly Explanations

The Early Internet (ARPANET): In the 1970s, the internet (then called ARPANET) was tiny. It consisted of only a few hundred computers located at specific universities and military bases. Because it was so small, everyone literally knew everyone else's computer.

The Master Spreadsheet (HOSTS.TXT): How did they translate names to IPs back then? They used a single text file called HOSTS.TXT. Imagine a master Excel spreadsheet maintained by one person at the Stanford Research Institute (SRI). If MIT added a new computer to the network, they had to call Stanford on the telephone and say, *"Please add MIT-Computer-1 at IP 10.0.0.5 to the list."* Stanford would update the master text file. Then, every other university in America had to manually download the new HOSTS.TXT file every single night so their computers would know how to find MIT.

4. The Breaking Point

By the early 1980s, the internet began growing rapidly. The HOSTS.TXT system became a catastrophic bottleneck:
  • Size: The text file became massive, taking too long to download over slow dial-up modems.
  • Name Collisions: What if MIT and Harvard both wanted to name their server Server-1? The text file didn't support duplicate names.
  • Central Point of Failure: If the Stanford computer holding the master file crashed, the entire global network was paralyzed. No one could update or download the phonebook.

5. The Invention of DNS (1983)

In 1983, an engineer named Paul Mockapetris designed a replacement system. Instead of one massive text file on one computer, he designed a decentralized, hierarchical database. He realized that instead of Stanford keeping track of MIT's computers, Stanford should just point to MIT, and MIT should be responsible for keeping track of its own computers! This hierarchical delegation was the birth of the modern Domain Name System (DNS).

6. Timeline Examples

  • 1969: ARPANET is born (the precursor to the Internet).
  • 1970s: The network relies entirely on the centralized HOSTS.TXT file.
  • 1983: Paul Mockapetris publishes RFC 882 and RFC 883, officially defining DNS.
  • 1985: The first .com domain name (symbolics.com) is registered.
  • 1990s: The World Wide Web explodes, and DNS proves it can scale infinitely.

7. Modern Infrastructure Legacy

Believe it or not, the HOSTS.TXT file still exists today on your computer! Operating systems (Windows, Mac, Linux) still check their local "hosts" file *before* they ask DNS.
bash
12345 
# On Windows, you can find your hosts file here:
C:\Windows\System32\drivers\etc\hosts

# On Mac/Linux, you can find it here:
/etc/hosts

Developers frequently edit this file to manually override DNS and force google.com to point to a local testing server on their laptop.

8. Best Practices

  • Never Edit the Hosts File for Production: While editing your local /etc/hosts file is great for local development, you should never rely on it for production infrastructure. If an IP address changes, you have to manually update every single computer's hosts file. Always use proper DNS records for production routing.

9. Common Mistakes

  • Assuming DNS is Centralized: Because of how simple it is to use, beginners often assume there is a "Google of DNS" that holds all the records. The genius of Mockapetris's invention was the exact opposite: DNS is a distributed web of millions of independent servers that query each other.

10. Mini Project: Edit Your Hosts File

Let's override the modern internet using the 1970s method.
  1. 1. (Windows) Open Notepad as Administrator. (Mac) Open Terminal and type sudo nano /etc/hosts.
  1. 2. Open your computer's hosts file.
  1. 3. Add this line at the very bottom:
127.0.0.1 youtube.com
  1. 4. Save the file.
  1. 5. Open your web browser and go to youtube.com.
  1. 6. *The Result:* It will fail to load! You just told your computer to route youtube.com to 127.0.0.1 (your own laptop). Your computer checked the local hosts file first and completely ignored global DNS!
*(Remember to delete that line and save when you are done!)*

11. Practice Exercises

  1. 1. Explain why the HOSTS.TXT method became mathematically and logistically impossible as the internet scaled to millions of devices.
  1. 2. How did the invention of DNS solve the "Name Collision" problem (e.g., two companies wanting the exact same server name)?

12. MCQs with Answers

Question 1

Before the invention of DNS, how did early internet computers resolve network names to IP addresses?

Question 2

Who is credited with inventing the Domain Name System (DNS) in 1983?

13. Interview Questions

  • Q: Explain the historical scaling problem that necessitated the transition from the HOSTS.TXT file to the Domain Name System.
  • Q: In a modern operating system, which is checked first for domain resolution: the local /etc/hosts file or the configured DNS server? How could a hacker exploit this?

14. FAQs

Q: Are any original domain names from the 1980s still active today? A: Yes! symbolics.com was the first .com registered in March 1985, and it is still online today serving as a museum of early internet history.

15. Summary

In Chapter 2, we traveled back to the dawn of networking to understand the origin of DNS. We explored the rigid, centralized limitations of the HOSTS.TXT file, recognizing that maintaining a single, manually updated spreadsheet of IP addresses was a catastrophic bottleneck for a growing internet. We celebrated Paul Mockapetris's invention of the Domain Name System—a highly scalable, decentralized hierarchy that delegated authority across the globe. Finally, we proved that the legacy of ARPANET lives on by manipulating the modern local hosts file to override global web traffic.

16. Next Chapter Recommendation

We know why DNS was built, but how does it actually execute a search across this massive global hierarchy today? Proceed to Chapter 3: Understanding How DNS Works.

Finish this Chapter

Save your progress on your learning path and prepare for coding interview challenges.

Previous Chapter Introduction to DNS
Next Chapter Understanding How DNS Works

Discussion

Join the discussion

Log in or create a free account to participate.

Sort: ·

Explore More

📖 Related Tutorials 4

🎥 Related Videos 2

🗺️ Related Roadmaps 1