Every time you type a web address into your browser, an invisible process runs in the background that transforms that familiar name into a number your computer can actually use. That process is DNS — the Domain Name System. Without it, navigating the internet would require memorising strings of numbers instead of names like google.com or wikipedia.org.
What Is DNS?
DNS stands for Domain Name System. It is a globally distributed database and protocol that maps human-readable domain names to numerical IP addresses. When you visit a website, your device does not actually know where example.com lives on the internet — it only understands IP addresses. DNS acts as the translator between the two.
Think of DNS as the internet's phone book. In the same way a phone book lets you look up a person's name and find their phone number, DNS lets your browser look up a domain name and find the corresponding IP address for the server hosting that site.
93.184.216.34. IPv6 addresses, used for the modern internet, look like 2606:2800:220:1:248:1893:25c8:1946. Humans prefer names; computers prefer numbers — DNS bridges that gap.Why Does DNS Exist?
In the earliest days of the internet (then called ARPANET), there were so few connected computers that a single text file called HOSTS.TXT was manually maintained and distributed to every machine. It mapped hostnames to IP addresses. As the network grew, this approach became unmanageable — the file grew too large, updates were too slow, and conflicts became common.
In 1983, Paul Mockapetris designed DNS as a scalable, distributed, and hierarchical replacement. Instead of a single file maintained by one organisation, DNS spread the responsibility across millions of servers worldwide, each authoritative for a portion of the namespace.
The DNS Hierarchy
DNS is structured as an inverted tree. At the top is the DNS root, represented by a single dot (.). Below the root are Top-Level Domains (TLDs) such as .com, .net, .org, and country codes like .uk or .de. Below TLDs sit second-level domains — the names organisations register, like showdns in showdns.net. Further levels can exist as subdomains, such as www or mail.
Root (.)
└── .net
└── showdns
├── www.showdns.net
└── mail.showdns.netHow a Domain Name Maps to an IP Address
When you type showdns.net into your browser, your operating system checks its local DNS cache first. If the answer is not cached, it sends a query to a recursive resolver — typically provided by your ISP or a public service like Google (8.8.8.8) or Cloudflare (1.1.1.1). The resolver then navigates the DNS hierarchy on your behalf:
- It asks a root nameserver where to find the
.netTLD servers. - It asks the .net TLD nameserver where to find
showdns.net's nameservers. - It asks the authoritative nameserver for
showdns.netfor the IP address. - The resolver returns the IP to your browser, which opens a connection to that address.
This entire process typically completes in under 100 milliseconds. Once resolved, the result is cached at multiple points so future lookups are even faster.
DNS Record Types
DNS stores information in resource records, each with a specific type and purpose. The most common types include:
- A record — maps a domain to an IPv4 address.
- AAAA record — maps a domain to an IPv6 address.
- CNAME record — creates an alias from one domain to another.
- MX record — specifies mail servers for a domain.
- TXT record — stores arbitrary text, used for verification and email security.
- NS record — lists the authoritative nameservers for a domain.
You can inspect any domain's DNS records using the ShowDNS DNS Lookup tool.
A Brief History of DNS
DNS has evolved significantly since its introduction in 1983. Key milestones include:
- 1983 — RFC 882 and RFC 883 published by Paul Mockapetris, defining DNS.
- 1987 — RFC 1034 and RFC 1035 replaced the originals with the foundational specifications still in use.
- 1997 — BIND (Berkeley Internet Name Domain) became the dominant DNS server software.
- 2005 — DNSSEC extensions ratified, adding cryptographic security to DNS responses.
- 2016 — Mirai botnet DDoS attack against Dyn highlighted the internet's dependence on DNS infrastructure.
- 2018 — DNS over HTTPS (DoH) and DNS over TLS (DoT) introduced to encrypt DNS queries and protect user privacy.
Why DNS Is Critical Infrastructure
DNS is not just a convenience — it is foundational infrastructure that almost every internet service depends on. Email delivery, website availability, API calls, and content delivery networks all rely on DNS functioning correctly. A DNS outage or misconfiguration can make an entire website or service unreachable, even if the underlying servers are perfectly healthy.
This is why monitoring DNS health matters. Tools like the DNS Propagation Checker let you verify that DNS changes have spread across the global network of resolvers.
DNS vs. Hosts File
Every operating system still maintains a local hosts file — a throwback to the pre-DNS era. Entries in this file take precedence over DNS lookups. Developers often use it to override DNS locally (for example, to test a new server before going live). However, for the public internet, DNS is the authoritative system that governs all name resolution.
# Example hosts file entry (Linux/macOS: /etc/hosts, Windows: C:\Windows\System32\drivers\etc\hosts)
127.0.0.1 localhost
192.168.1.10 myserver.localFrequently Asked Questions
What does DNS stand for?
DNS stands for Domain Name System. It is the protocol and distributed database that translates human-readable domain names like example.com into the numerical IP addresses that computers use to communicate over the internet.
Who controls DNS?
DNS is governed in a distributed way. ICANN (Internet Corporation for Assigned Names and Numbers) oversees the root zone and the delegation of TLDs. Each TLD is managed by a registry (for example, Verisign manages .com). Individual domain owners manage their own zones through their registrar and DNS hosting provider.
Can DNS be wrong or manipulated?
Yes. DNS can be misconfigured by the domain owner, or it can be manipulated by attackers through a technique called DNS spoofing (also known as DNS cache poisoning), where false records are injected into a resolver's cache. DNSSEC was designed to prevent this by cryptographically signing DNS records.
How is DNS different from a search engine?
DNS resolves exact domain names to IP addresses. It has no concept of search queries. A search engine like Google indexes web content and returns results based on relevance. DNS operates at a lower level — it just finds where a known address lives, not what that address contains.
Is DNS the same as a domain registrar?
No. A domain registrar is a company where you purchase and register a domain name (such as Namecheap or GoDaddy). DNS hosting is the service that actually stores and serves your DNS records. These can be the same provider or different ones — many people register domains with one company but host DNS with another, like Cloudflare.