What Is DNS (Domain Name System)?

Learn how the Domain Name System works, including recursive and iterative queries, root servers, caching, and TTL values. A technical overview referencing RFC 1035.

What Is DNS (Domain Name System)?

The Domain Name System (DNS) is a hierarchical, distributed naming system that translates human-readable domain names (like inboxtooling.com) into machine-readable IP addresses (like 93.184.216.34). Defined originally in RFC 1034 and RFC 1035, DNS is often described as the phone book of the internet.

How DNS Resolution Works

When you type a URL into your browser or send an email to [email protected], a multi-step lookup process begins:

Recursive Queries

Your device sends a query to a recursive resolver, typically operated by your ISP or a public DNS service like Cloudflare (1.1.1.1) or Google (8.8.8.8). The recursive resolver is responsible for chasing down the answer on your behalf. It either returns a cached response or performs a series of iterative queries to find the authoritative answer.

Iterative Queries

The recursive resolver queries DNS servers in sequence, each one referring it closer to the answer:

  1. Root servers. The resolver queries one of the 13 root server clusters (named A through M). The root server does not know the IP for example.com, but it knows which servers are authoritative for .com and returns an NS referral.
  2. TLD servers. The resolver queries the .com TLD servers (operated by Verisign). These servers return the NS records for example.com, pointing to the domain's authoritative name servers.
  3. Authoritative servers. The resolver queries the authoritative name server for example.com, which returns the requested record (A, MX, TXT, etc.).

The resolver caches the final answer and returns it to your device.

Caching and TTL

Every DNS record includes a Time to Live (TTL) value, measured in seconds, that tells resolvers how long to cache the response. A TTL of 3600 means the record can be cached for one hour before the resolver must query the authoritative server again.

Short TTLs (60-300 seconds) allow fast propagation of changes but increase query load on authoritative servers. Long TTLs (3600-86400 seconds) reduce query volume but delay propagation when you update records. For email-related records like MX and SPF TXT records, a TTL of 3600 is a common balance.

DNS Server Roles

  • Recursive resolver. Accepts queries from clients and performs the full resolution chain. Caches results.
  • Root name server. The entry point for all DNS resolution. Thirteen logical servers, operated by organizations including Verisign, ICANN, the U.S. Department of Defense, and various universities and nonprofits.
  • TLD name server. Authoritative for a top-level domain (.com, .org, .net, country codes). Returns NS referrals for individual domains.
  • Authoritative name server. Holds the actual DNS zone for a domain and returns definitive answers for records within that zone.

Why DNS Matters for Email

Email delivery depends entirely on DNS. When a mail server wants to deliver a message to [email protected], it queries DNS for the MX records of example.com. Those MX records point to the mail servers that accept email for that domain. Beyond routing, DNS hosts the TXT records that define SPF policies, the CNAME or TXT records for DKIM public keys, and the TXT records for DMARC policies.

A misconfigured DNS record can silently break email delivery, authentication, or both. Use our DNS lookup tool to query any domain's records and verify correct configuration.


Stay on top of your email infrastructure. Sign up for the InboxTooling newsletter for deliverability tips, tool updates, and best practices.