DNS
Abbreviation · Development · Origin: 1983
Definitions
DNS, or Domain Name System, is the hierarchical naming system that translates human-readable domain names (like google.com) into the numeric IP addresses that computers use to route traffic. Often called the 'phonebook of the internet,' DNS makes it possible to navigate the web using memorable names instead of remembering strings of numbers. When you type a URL into your browser, a DNS resolver queries a chain of authoritative name servers, starting from the root servers, then the TLD (top-level domain) servers, and finally the authoritative server for that domain, to find the correct IP address. DNS records come in many types: A records map names to IPv4 addresses, AAAA records to IPv6, CNAME records create aliases, MX records direct email, TXT records hold verification data, and NS records delegate authority. DNS responses are cached at multiple levels (browser, operating system, ISP) to reduce lookup latency. DNS is critical infrastructure, and misconfigurations or attacks like DNS spoofing can redirect users to malicious sites.
In plain English: The internet's phone book — converts website names you can remember (like google.com) into the actual numbers computers use to find each other.
DNS is the most critical yet invisible infrastructure on the internet. A DNS outage takes down everything — email, websites, APIs — because nothing can find anything else. The 2016 Dyn attack proved that DNS is a single point of failure for the entire internet.
Example: 'When Dyn's DNS went down, Twitter, Netflix, Reddit, and GitHub all went offline simultaneously. Nobody thinks about DNS until it breaks.'
Source: infrastructure criticality
Origin Story
The internet's phone book that nobody appreciates until it breaks
The **Domain Name System** was designed by **Paul Mockapetris** in 1983 (RFC 882 and 883) to solve a problem that was becoming unmanageable: the early internet relied on a single file called `HOSTS.TXT`, maintained by the Stanford Research Institute's Network Information Center. Every computer on the network had to download this file to map hostnames to IP addresses. As the network grew, this centralized approach was collapsing under its own weight.
Mockapetris designed DNS as a distributed, hierarchical database. Instead of one file, name resolution was delegated across a tree of authoritative servers: root servers pointed to `.com` servers, which pointed to `example.com` servers, and so on. The system was elegant, scalable, and became the foundation of the internet as we know it.
DNS is often called the internet's phone book, but it's more like the entire postal addressing system. Every web request, email delivery, and API call begins with a DNS lookup. When DNS breaks, the internet effectively stops working, as demonstrated by several high-profile outages that took down major services.
Coined by: Paul Mockapetris
Context: RFC 882/883, November 1983
Fun fact: The original HOSTS.TXT file that DNS replaced was literally emailed around. Network administrators had to periodically FTP a new copy from Stanford. By 1983, the file was changing so rapidly that it was effectively out of date by the time you downloaded it.