What Is DNS? The Domain Name System Explained Simply

DNS (Domain Name System) is the internet's address book. It translates human-readable domain names — like example.com — into the numerical IP addresses that computers use to find and talk to each other. Without DNS, you'd need to memorize strings of numbers like 93.184.216.34 just to visit a website. DNS handles that translation automatically every time you open a browser.

This guide explains what DNS is, how it works, what the different record types mean, and what you need to know about it when managing a website or domain.

Why DNS exists

Every device on the internet — servers, computers, phones — is identified by a numerical address called an IP address (Internet Protocol address). IPv4 addresses look like 192.168.1.1; newer IPv6 addresses look like 2001:0db8:85a3:0000:0000:8a2e:0370:7334.

These numbers are how computers communicate, but they're impossible for humans to remember reliably. DNS solves this by creating a mapping between memorable domain names (google.com, yoursite.com) and the underlying IP addresses. Type a domain name into your browser, and DNS quietly looks up the right IP address and sends you there — in milliseconds.

How DNS works: the lookup process step by step

When you type a URL into your browser and press Enter, a series of lookups happen almost instantaneously. Here's what's going on behind the scenes:

Step 1: Check the local cache

Your device first checks its own DNS cache — a temporary store of recent DNS lookups. If you visited example.com an hour ago and the record hasn't expired, your computer already knows the IP address and skips all subsequent steps.

Step 2: Query the recursive resolver

If the answer isn't cached locally, your request goes to a recursive resolver — typically operated by your internet service provider (ISP), or a public DNS provider like Google (8.8.8.8) or Cloudflare (1.1.1.1). The resolver acts as a middleman, doing the work of finding the right answer on your behalf.

Step 3: Ask the root nameserver

If the recursive resolver doesn't have the answer cached either, it queries one of the internet's 13 root nameserver clusters. Root nameservers don't know the IP address for example.com, but they do know which nameservers are responsible for the .com extension.

Step 4: Ask the TLD nameserver

The root nameserver refers the resolver to the TLD (Top-Level Domain) nameserver for .com. The TLD nameserver knows which authoritative nameservers are responsible for example.com specifically.

Step 5: Ask the authoritative nameserver

The resolver now queries the authoritative nameserver for example.com — the server that actually holds the DNS records for that domain, including the IP address. It returns the final answer.

Step 6: Return the result and cache it

The recursive resolver receives the IP address, returns it to your browser, and caches it for future lookups. Your browser connects to the web server hosting example.com, and the page loads. All of this typically happens in under 100 milliseconds.

The four types of DNS servers

• Recursive resolver — receives your query, does the work of finding the answer, returns it to you

• Root nameserver — knows which TLD nameservers to contact; doesn't store domain-specific records

• TLD nameserver — manages a top-level domain (.com, .org, .net); knows which authoritative servers handle each domain

• Authoritative nameserver — the final source of truth; holds the actual DNS records for a domain

When you register a domain and connect it to a hosting provider, you're telling the TLD nameserver: for this domain, the authoritative nameserver is over there. You do that by setting your domain's nameservers to point to your host.

DNS record types explained

• A record (Address): maps a domain name to an IPv4 address — most common record type

• AAAA record: maps a domain name to an IPv6 address

• CNAME record (Canonical Name): creates an alias — points one domain name to another domain name

• MX record (Mail Exchange): tells mail servers where to deliver email for your domain

• TXT record: stores arbitrary text — used for email verification (SPF, DKIM), domain ownership verification, and security

• NS record (Nameserver): specifies which nameservers are authoritative for your domain

• SOA record (Start of Authority): contains administrative info about the domain; required for every zone

• CAA record (Certification Authority Authorization): specifies which certificate authorities can issue SSL certificates for your domain

A record (the most important one for websites)

The A record is what makes your domain point to your web server. When you connect a domain to a website builder or hosting provider, you're usually setting an A record that points your domain (example.com) to the IP address of your host's server. Example: example.com → 93.184.216.34

CNAME record (alias)

A CNAME record doesn't point to an IP address — it points to another domain name. It's used for subdomains and for integrating third-party services. Important: you can't use a CNAME record on a root domain (example.com). CNAMEs only work on subdomains.

MX record (email routing)

MX records tell other mail servers where to deliver email sent to your domain. Without correct MX records, email to yourname@yourdomain.com won't be delivered. MX records include a priority number — lower numbers get tried first. If your primary mail server is down, mail servers fall back to the one with the next lowest priority.

TXT record (verification and authentication)

TXT records are multipurpose text entries used to: verify domain ownership (Google Search Console asks you to add a TXT record to prove you own the domain), set up SPF (Sender Policy Framework) to prevent spoofing, configure DKIM (DomainKeys Identified Mail) to add cryptographic signatures to outgoing emails, and set DMARC policies.

What is TTL?

TTL stands for Time-To-Live. Every DNS record has a TTL value measured in seconds that tells resolvers how long to cache the record before checking again.

• TTL of 86400 = cache for 24 hours

• TTL of 3600 = cache for 1 hour

• TTL of 300 = cache for 5 minutes

Before making a significant DNS change (switching hosts, changing nameservers), lower your TTL to 300 seconds 24-48 hours in advance. This means resolvers will re-check much more frequently, and your changes will propagate faster once you make them.

DNS propagation: why changes take time

When you update a DNS record, the change doesn't instantly reach every DNS resolver on earth. Resolvers around the world have cached your old record and will keep using it until that cache expires based on your TTL. As caches expire and resolvers fetch the new record, your changes gradually spread — a process called DNS propagation.

Typical propagation times:

• A and AAAA records: usually a few minutes to a few hours

• CNAME records: a few minutes to 24 hours

• MX records: up to 48 hours (mail systems cache longer for stability)

• TXT records: up to 72 hours

• NS records (nameserver changes): 48-72 hours — the slowest, because they affect everything underneath

You can check propagation status using whatsmydns.net, which shows whether your new DNS records are resolving correctly across different locations worldwide.

Public DNS servers: what they are and when to use them

By default, your device uses the DNS servers provided by your ISP. Popular alternatives you can configure yourself:

• Google Public DNS: 8.8.8.8 / 8.8.4.4

• Cloudflare (privacy-focused, fastest): 1.1.1.1 / 1.0.0.1

• OpenDNS: 208.67.222.222 / 208.67.220.220

• Quad9 (security-focused): 9.9.9.9 / 149.112.112.112

Switching to a public DNS server on your router or device can improve browsing speed and privacy. Cloudflare's 1.1.1.1 is widely considered the fastest public DNS resolver.

DNS and security: what can go wrong

DNS is a foundational internet protocol designed in an era when security wasn't the top priority. That creates some vulnerabilities worth knowing about:

• DNS hijacking (DNS spoofing): an attacker redirects your DNS queries to send you to a fake website instead of the real one

• DNS cache poisoning: attackers inject false records into a resolver's cache, causing it to send users to malicious sites

• DNSSEC (DNS Security Extensions): adds cryptographic signatures to DNS records, allowing resolvers to verify records haven't been tampered with

• DNS over HTTPS (DoH) and DNS over TLS (DoT): encrypt DNS queries to prevent eavesdropping

• 
  

How DNS fits into owning a domain

If you own a domain, you'll encounter DNS settings constantly. You'll typically manage:

• Setting your nameservers — pointing your domain at your host's nameservers

• Editing A records to connect your domain to a web host

• Adding CNAME records for subdomains pointing to third-party services

• Setting up MX records for professional email

• Adding TXT records for domain ownership verification and email authentication (SPF, DKIM, DMARC)

The fastest way to get DNS configured correctly is to use an all-in-one platform. Use domain name search to find an available domain and buy a domain through Wix — DNS is configured for you when you connect your domain to your Wix site.

Common DNS mistakes and how to avoid them

• Forgetting to lower TTL before a big change — set TTL to 300 seconds 24-48 hours before switching hosts

• Using a CNAME on a root domain — CNAME records only work on subdomains, not example.com itself

• Getting MX records wrong — incorrect MX records mean domain email stops receiving mail, often quietly

• Not setting up SPF/DKIM/DMARC — without email authentication, your domain email lands in spam or can be spoofed

• Deleting all DNS records before adding new ones — always add new records first and verify they work before removing old ones

  
  

What is DNS FAQ

What does DNS stand for?

DNS stands for Domain Name System. It's the global, distributed system that translates human-readable domain names (like example.com) into numerical IP addresses that computers use to communicate.

Who controls DNS?

DNS is a distributed system with no single controlling authority. ICANN (Internet Corporation for Assigned Names and Numbers) oversees the root zone and coordinates TLD registries. Individual domain owners control their own DNS records through their domain registrar or hosting provider.

What happens if DNS goes down?

If the DNS server your device is using becomes unavailable, you can't resolve domain names — websites appear inaccessible. This happened famously in 2016 when a DDoS attack on a major DNS provider made large portions of the internet unreachable. Sites mitigate this by using hosting providers with redundant DNS infrastructure.

Is DNS the same as a domain name?

No. A domain name is the address itself (example.com). DNS is the system that translates that address into an IP address. The domain name is what you register; DNS is the infrastructure that makes it work.

Can DNS affect website speed?

Yes. Slow DNS resolution adds latency before a page starts loading. Using a fast recursive resolver like Cloudflare's 1.1.1.1, optimizing your TTL values, and using a CDN can all contribute to faster load times.

What is a DNS record?

A DNS record is an entry in a domain's DNS zone file that maps a name to a value. Different record types serve different purposes: A records point to IP addresses, MX records direct email, TXT records store verification strings, and so on.

What is a DNS zone?

A DNS zone is the portion of the DNS namespace managed by a specific organization or administrator. Your domain's zone file contains all the DNS records for your domain and any subdomains you configure.

How do I find my DNS records?

You can look up DNS records for any domain using tools like MXToolbox or DNS Checker. Your domain registrar or hosting panel also shows your own domain's DNS records.

What is a nameserver?

A nameserver is a server that stores DNS records for a domain and answers queries about it. When you set your domain's nameservers to point to your hosting provider, you're telling the internet where to look for your domain's DNS records.

Can I use different companies for my domain and my DNS?

Yes. Many people register their domain with one company and manage DNS with another. You simply set your domain's nameservers to point to wherever you want to manage DNS. The domain registrar only needs to know which nameservers to use.