What is DNS?

If you already understand what a domain name is, the next layer is the system that makes domain names work. Every website, every email, every app that connects to a server depends on DNS running quietly in the background. Without it, the internet would be a grid of numbered addresses with no names attached.

What is a DNS?

DNS stands for domain name system. It is a global network of servers that translates human-friendly domain names into machine-readable IP addresses. When you type a domain into your browser, your computer does not know where that name lives. It needs a number. DNS is the system that finds that number.

Think of it like the contacts app on your phone. You tap a person's name and your phone dials the right number. You never memorize the number itself. DNS works the same way for the internet. You provide the name, and DNS returns the number your browser needs to reach the correct server.

The phone book comparison shows up often, but DNS goes further than a phone book ever could. A phone book is printed once and gets outdated fast. DNS updates in real time. When a website moves to a new server, DNS records change and the whole internet adjusts within hours. It is a living, constantly updated directory that handles billions of lookups every day.

Why does DNS exist?

Computers communicate using IP addresses. An IP address is a string of numbers like 93.184.216.34 that points to one specific server. Every device connected to the internet has at least one. The problem is that people are terrible at remembering long numbers.

DNS was created to solve that gap. Instead of asking people to memorize IP addresses for every site they visit, DNS lets them use plain names. You type the name. DNS converts it. Your browser reaches the server. The whole thing happens without you thinking about it.

Without DNS, you would need to look up and type the IP address for every website you want to visit. Bookmarks would be rows of numbers. Links in emails would be unreadable. The internet as you know it would not function for everyday use.

How does a DNS lookup work?

Every time you visit a website, a DNS lookup runs in the background. It follows a specific path through several servers, each one narrowing down the answer until your browser gets the IP address it needs. The full process takes milliseconds. Here is every step.

Step 1. Your browser checks its own cache

Before asking anyone else, your browser checks if it already knows the answer. If you visited the same site recently, the IP address may still be saved in your browser's local cache. If it is there, the lookup ends immediately and your browser loads the page. No outside servers needed.

Step 2. Your operating system checks its cache

If your browser does not have the answer, it asks your computer's operating system. Your OS keeps its own DNS cache, separate from the browser. It may have the IP address stored from a different browser or a different app that visited the same domain. If the OS has it, the lookup stops here.

Step 3. The request goes to a recursive resolver

When neither the browser nor the OS has the answer, the request leaves your computer. It goes to a recursive resolver, which is a DNS server usually run by your internet provider. The resolver's job is to track down the IP address on your behalf. It does not have the answer yet, but it knows the chain of servers to ask.

The resolver also has its own cache. If another user on the same network visited that domain recently, the resolver may already have the IP address stored. If it does, it sends the answer back and the lookup ends. If not, the resolver starts working its way through the DNS hierarchy.

Step 4. The resolver contacts a root nameserver

The first stop is one of the internet's root nameservers. There are 13 sets of root nameservers, labeled A through M, spread across the globe. Each set runs on hundreds of physical servers. The root nameserver does not know the IP address of your domain. What it does know is which server handles the domain extension you are looking for. If you are visiting a .com domain, the root server points the resolver to the .com TLD nameserver.

Step 5. The TLD nameserver narrows it down

TLD stands for top-level domain. The TLD nameserver for .com knows about every .com domain registered on the internet. It does not hold the final IP address, but it knows which authoritative nameserver is responsible for the specific domain you want. It sends that information back to the resolver.

Step 6. The authoritative nameserver returns the IP address

The authoritative nameserver is the last stop. This server holds the actual DNS records for the domain, including the A record that maps the domain name to an IP address. It sends the IP address back to the resolver. The resolver caches the answer for future lookups and passes it along to your browser.

Step 7. Your browser connects and loads the page

With the IP address in hand, your browser sends a request directly to that server. The server responds with the website files, and the page loads on your screen. The entire chain, from your first keystroke to the finished page, typically completes in under 100 milliseconds.

What happens when DNS fails?

DNS is invisible when it works. When it breaks, the effects are immediate and often confusing because the symptoms look like something else.

• Your website stops loading. If the DNS record pointing to your web server is wrong or missing, browsers cannot find your site. Your domain still belongs to you, but visitors see an error page instead of your content.
• Email stops arriving. Email depends on MX records in your DNS settings. If those records are deleted or pointed at the wrong server, messages sent to your domain bounce or vanish.
• SSL certificates fail to renew. Some SSL verification methods rely on DNS records. Remove or change those records and the renewal breaks, leaving your site without a secure connection.
• Third-party tools disconnect. Services like email marketing tools or analytics verification often require specific DNS records. Changing or removing those records cuts the connection.
• Visitors see different results depending on location. During DNS propagation (the period after you update a record), some DNS servers still have the old information cached. Some visitors reach the new server. Others reach the old one. This can last up to 48 hours.

Most DNS problems come down to a wrong record, a missing record, or a change that has not finished spreading across the internet. The fix is usually straightforward once you know which record to check.

How do your domain's DNS settings control traffic?

Your domain's DNS settings are the control panel for where your traffic goes. Every service connected to your domain, from your website to your email to your analytics tools, is routed through DNS records.

When you finish registering a domain, one of the first things you set up is DNS. You point your domain's A record to the server where your website is hosted. You set MX records so email knows where to go. You add TXT records so third-party services can verify you own the domain.

Change any of those records and traffic shifts. Point your A record at a new server and your website moves. Update your MX records and your email starts flowing to a different provider. DNS is what gives you control over every connection tied to your domain.

This is also why understanding the difference between domain vs hosting matters. Your domain is the name. Your hosting is the server. DNS is the bridge that connects the two. Without the right DNS settings, your domain and your hosting do not talk to each other.

What is the difference between DNS and a registrar?

DNS and your domain registrar are two separate things, even though they often come from the same company.

Your registrar is the company where you buy and manage your domain name. It handles the registration, the renewal, and the ownership records. DNS is the system that translates your domain name into an IP address so the internet can route traffic to the right place.

You can register a domain at one company and use DNS servers at a completely different one. Many brands do this. They buy the domain at one registrar and point the nameservers to their hosting provider's DNS. The registrar manages ownership. The DNS provider manages routing.

The confusion happens because most registrars also offer DNS management built in. So when you log into your registrar and see a DNS settings page, it feels like they are the same thing. They are not. One is about who owns the domain. The other is about where the domain sends traffic.

DNS terms you should know

DNS has its own set of terms. You do not need to memorize all of them, but knowing the basics helps when you are setting up a website or troubleshooting a problem.

• Nameserver. The server that stores DNS records for a domain. When someone asks "where does this domain point?", the nameserver has the answer.
• Resolver. The server that receives your DNS query and works through the chain of nameservers to find the IP address. Your internet provider runs one, and so do public DNS services.
• A record. The DNS record that maps a domain name to an IPv4 address (like 93.184.216.34). This is the record that connects your domain to the server where your website lives.
• CNAME record. A record that points one domain name to another domain name. Often used for subdomains, so www.yourdomain.com points to the same place as yourdomain.com.
• MX record. The record that tells the internet which server handles email for your domain. Without a correct MX record, email to your domain will not be delivered.
• TTL (time to live). A value on each DNS record that controls how long other servers cache it before checking for an update. Shorter TTLs mean faster updates but more frequent lookups.

The next chapter in this series covers DNS record types in full detail, including when to use each one and how to set them up correctly.

How WEMASY handles DNS

When you build a site with WEMASY and connect your own domain, WEMASY gives you the exact DNS records to enter. The platform guides you through each step so you know which records to add and where. SSL is set up automatically, which means you do not need to create DNS records for certificate verification on your own.

For brands that want to skip the technical setup, WEMASY keeps things simple. You register your domain, follow the guided steps, and the platform connects your domain to your live site. See what each plan includes at WEMASY pricing.

What comes next

This article covered what DNS is, how a DNS lookup moves through the internet, and why DNS settings matter for every domain. The next chapter goes deeper into DNS servers specifically, explaining the different types of servers involved, how they are organized, and what role each one plays in keeping the internet running.

Frequently asked questions about DNS