What Is DNS? A Simple Guide for Website Owners

DNS — the Domain Name System — is the part of how the internet works that almost nobody explains clearly, despite every website owner needing to touch it eventually. Here's the plain-English version.

The core idea. Computers on the internet find each other using numerical IP addresses, not names — but humans remember "yourbusiness.com" far more easily than a string of numbers. DNS is the system that translates the domain name you type into a browser into the actual IP address of the server hosting that website, functioning essentially as the internet's phone book.

How a DNS lookup actually happens. When you type a domain into your browser, your computer asks a DNS resolver (often run by your internet provider) to look up that domain. The resolver checks a chain of DNS servers — starting broad (which servers handle .com domains) and narrowing down (which specific server handles yourbusiness.com) — until it finds the actual IP address, which it returns to your browser so it can connect to the right server. This entire process typically takes a fraction of a second.

The DNS records you'll actually encounter. An A record points a domain (or subdomain) directly to an IPv4 address — this is the most common record connecting a domain to a web server. A CNAME record points a domain to another domain name rather than directly to an IP address, often used for subdomains that should follow a main domain's configuration. An MX record specifies which mail servers handle email for the domain, and in what priority order. A TXT record holds arbitrary text data, commonly used for domain verification and for the SPF/DKIM email authentication records covered elsewhere. An NS record specifies which nameservers are authoritative for the domain — essentially, which company's DNS system is in charge of all the domain's other records.

Nameservers versus individual DNS records. There are two ways to point a domain at a new host: change the nameservers entirely (handing over full DNS management to the new provider) or edit individual records like the A record while keeping DNS management with your registrar. Nameserver changes are simpler when moving everything to one provider; individual record edits give more granular control when different services (hosting, email) are split across providers.

Why DNS changes aren't instant. Every DNS record has a TTL (Time To Live) value that tells other servers how long to cache that information before checking for updates again — commonly anywhere from a few minutes to 24 hours. This is why DNS changes "propagate" gradually across the internet rather than updating everywhere simultaneously, and why a freshly changed domain might show the old server to some visitors and the new one to others for a period after the change.

Why understanding this actually matters. Almost every website task that goes wrong in a confusing way — email suddenly not arriving, a site showing an old version after a host migration, an SSL certificate failing to verify — traces back to a DNS record that's missing, incorrect, or still propagating. Understanding what DNS actually is turns those situations from mysterious into diagnosable.