Every device on a public network has an address. For the web that is usually an IPv4 address such as 93.184.216.34 or an IPv6 address that is even less friendly to type. DNS exists so you can ask for example.com instead. The system is distributed on purpose. No single company stores every name, and no single outage is supposed to take the whole namespace down.
Names, zones, and records
A domain name is a path through a tree. The unnamed root sits at the top. Below it are top-level domains (TLDs) such as com and uk. Below those are registered domains, then subdomains. The slice of the tree one administrator controls is a zone. Inside a zone, resource records attach data to names: addresses, mail servers, text policies, aliases, and more. DNSFetch’s job is to fetch those records and show them without a terminal.
What DNS is not
DNS is not a web host. Changing an A record does not copy files; it only changes where browsers look. DNS is not email itself; MX records only name the servers that speak SMTP. DNS is not a certificate. TLS still has to succeed after the address is known, which is why CAA records and ACME HTTP-01 challenges show up in the same troubleshooting session as A records.
Who runs it
ICANN coordinates the root and TLD policies. Registries operate TLDs. Registrars sell names. You (or your DNS host) run the authoritative nameservers for your zone. Recursors — often your ISP, or 1.1.1.1, 8.8.8.8, 9.9.9.9 — cache answers so the root is not asked for com a billion times a day. When a lookup “has not propagated,” you are almost always looking at a cache, not a planet-wide delay. That is covered in DNS propagation.
Why operators still stare at DNS daily
Migrations, SaaS domain verification, mail cutovers, and CDN onboarding are all DNS chores. A single typo in an MX target or an SPF include can look like a product outage. Learning the handful of record types in the field guide pays off faster than most other ops trivia. Then run a live lookup on your own domain and see whether the internet agrees with your control panel.
A 30-second mental model
- You type a name.
- Your stub resolver asks a recursive resolver.
- The recursor asks root → TLD → authoritative, unless a cache already has a still-fresh answer.
- An A or AAAA (or a CNAME chain that ends in one) comes back.
- The application connects to that address.
The next article, how DNS works, slows that path down hop by hop.