Products Solutions Templates Pricing Resources

What is a DNS server?

Home / Everything About / Everything About Domains / What is a DNS server?

If you have read the chapter on what DNS is, you already know the domain name system translates names into IP addresses. A DNS server is one of the machines that makes that translation happen. There is not just one. There are millions of DNS servers around the world, each playing a specific role in the lookup chain.

What is a DNS server in simple terms?

A DNS server is a computer that stores domain name information and responds to lookup requests. When your browser needs to find a website, it asks a DNS server. That server either has the answer stored already or knows which other server to ask next.

Think of it like calling a help desk. You ask for a person's phone number. The person at the desk might know it off the top of their head, or they might need to check with someone else. Either way, you get the number back and can make your call. A DNS server works the same way. You give it a domain name, and it gives back the IP address your browser needs to load the site.

The dns server meaning is straightforward. It is a server dedicated to the domain name system. Its only job is to help translate names into numbers so devices can find each other on the internet.

What are the four types of DNS servers?

Not every DNS server does the same thing. There are four types, and each one handles a different step in the lookup process. Understanding how DNS servers work means understanding what each type does and when it gets involved.

Recursive resolver

The recursive resolver is the first server your browser talks to. It is usually run by your internet provider. When you type a domain name and hit enter, the request goes to this server first. The resolver does not hold the final answer for most domains. Instead, it does the legwork. It contacts other servers on your behalf, collects the answer, and sends it back to your browser.

Think of the recursive resolver as a librarian. You ask for a book. The librarian does not have every book memorized, but they know how to find it. They check the catalog, walk to the right shelf, grab the book, and hand it to you. The resolver does the same thing with IP addresses.

The resolver also saves answers it has already looked up. This is called caching. If someone else on the same network asked for the same domain five minutes ago, the resolver already has the answer stored and can skip the rest of the steps.

Root nameserver

If the resolver does not have the answer cached, its first stop is a root nameserver. There are 13 sets of root nameservers spread across the globe. They sit at the very top of the DNS system.

A root nameserver does not know the IP address of any specific website. What it does know is which server handles each domain extension. If you are looking for a .com domain, the root nameserver tells the resolver where to find the .com servers. If you are looking for a .org domain, it points to the .org servers.

Root nameservers are the starting point of every DNS lookup that is not already cached. They do not answer the question, but they always know where to send it next.

TLD nameserver

TLD stands for top-level domain. The TLD nameserver handles all domains under a specific extension. The .com TLD nameserver knows about every .com domain. The .net TLD nameserver knows about every .net domain.

When the recursive resolver reaches the TLD nameserver, it asks, "Which server is in charge of this specific domain?" The TLD nameserver does not return the final IP address. It returns the address of the authoritative nameserver for that domain. This is the server that has the actual answer.

Authoritative nameserver

The authoritative nameserver is the final stop. This is the server that holds the actual DNS records for a domain. It knows the IP address where the website lives, where email should go, and every other record the domain owner has set up.

When the recursive resolver reaches the authoritative nameserver, it gets the IP address it has been looking for. The resolver sends that address back to your browser, your browser connects to the web server at that address, and the page loads.

How do these DNS servers work together?

Every DNS lookup follows the same chain. Here is what happens from the moment you type a domain to the moment the page starts loading.

You type a domain name into your browser and press enter.
Your browser checks its own cache. If it visited this site recently, it may already have the IP address saved.
If not, the request goes to the recursive resolver (usually your internet provider's server).
The resolver checks its cache. If it has a recent answer, it sends it back immediately.
If not, the resolver contacts a root nameserver. The root nameserver says, "For .com domains, go talk to this TLD nameserver."
The resolver contacts the TLD nameserver. The TLD nameserver says, "For this specific domain, go talk to this authoritative nameserver."
The resolver contacts the authoritative nameserver. The authoritative nameserver returns the actual IP address.
The resolver sends the IP address to your browser and caches it for next time.
Your browser connects to the IP address and the web page loads.

This entire process takes milliseconds. You never see it happening, but it runs every single time you visit a website, send an email, or use any online service.

What happens when a DNS server is slow or goes down?

If any DNS server in the chain is slow or unreachable, you feel it immediately. The symptoms look like this.

Pages take a long time to start loading. A slow recursive resolver adds delay before your browser even begins downloading the page. The site itself might be fast, but the DNS lookup that comes first is holding everything up.
Websites fail to load entirely. If the resolver cannot reach the root, TLD, or authoritative nameserver, the lookup fails and your browser shows an error. The website is still online, but your device cannot find it.
"DNS server not responding" errors. This means your device cannot reach the recursive resolver at all. Without that first server in the chain, no lookups can happen and no websites load.
Some sites work while others do not. Cached lookups still work. Sites you visited recently may load fine because the resolver already has their IP addresses saved. New sites fail because the resolver cannot complete fresh lookups.

DNS outages are rare at the root and TLD level because those systems are built with heavy backup. The most common point of failure is the recursive resolver, which is the server your internet provider runs, or the authoritative nameserver, which is the one your domain or hosting provider manages.

What is the difference between public DNS and private DNS?

By default, your device uses the recursive resolver provided by your internet provider. This is your private DNS server. It works automatically. You did not choose it and you probably never noticed it.

A public DNS server is an alternative recursive resolver run by a different company. Anyone can switch to one. Public DNS servers are built to be fast, reliable, and available worldwide.

The main reasons people switch from their internet provider's DNS to a public DNS server include the following.

Speed. Some public DNS servers respond faster than the default one from your internet provider, especially if your provider's servers are overloaded or located far away.
Reliability. Public DNS servers are designed with heavy backup systems. If one server goes down, another picks up the request. Your internet provider's DNS may not have the same level of backup.
Filtering. Some public DNS servers offer built-in content filtering, blocking known harmful websites before they load. This adds an extra layer of protection without installing anything on your device.

Switching does not change your internet provider or your internet speed overall. It only changes which server handles your DNS lookups.

Can you change your DNS server?

Yes. You can change which DNS server your device uses, and it takes less than five minutes.

On most computers and phones, there is a network settings screen where you can enter a preferred DNS server address. You replace the automatic setting with the address of the public DNS server you want to use. Once saved, your device sends all DNS lookups to that server instead of your internet provider's default.

You can also change the DNS server at the router level. If you update the DNS settings on your router, every device on your home or office network uses the new server automatically, without changing settings on each device individually.

Reasons you might want to change your DNS server include the following.

Your current DNS is slow and pages take too long to start loading.
You want the built-in content filtering that some public DNS servers provide.
Your internet provider's DNS server has had outages and you want something more reliable.

Is a DNS server the same as a nameserver?

These two terms overlap, and that causes confusion. Here is the short version.

A nameserver is any server that holds DNS records for a domain and responds to queries about that domain. An authoritative nameserver is a nameserver. A root nameserver is a nameserver. They all hold DNS data and respond to requests.

A DNS server is a broader term. It includes nameservers, but it also includes recursive resolvers, which do not hold DNS records themselves. Resolvers just go out and find the answers from nameservers.

In everyday use, many people say "DNS server" and "nameserver" to mean the same thing. When your hosting provider says "point your domain to our nameservers," they mean the authoritative nameservers that hold your site's DNS records. When someone says "change your DNS server," they usually mean the recursive resolver your device uses for lookups.

The next chapter in this series covers nameservers in full detail, including what they store, how to find yours, and when you need to change them.

How WEMASY handles DNS servers

When you connect a domain to your WEMASY site, WEMASY tells you exactly which nameserver settings to use. You update the DNS records at your domain registrar as guided, and WEMASY handles the connection from there. SSL is set up automatically, and you do not need to configure any extra DNS records for security certificates.

The platform removes the guesswork from the DNS setup process. You follow the steps, the records update, and your site goes live under your domain. See what is included in each plan at WEMASY pricing.