If you already know what a domain name is, the next question is how that name gets you to a website. That is where DNS comes in. It is the layer between the name you type and the server that holds your site.
What is DNS?
DNS stands for domain name system. It is a global network of servers that converts human-readable domain names into IP addresses. An IP address is a string of numbers that identifies a specific server on the internet. When you type a domain into your browser, DNS finds the matching IP address and sends your browser to the right server.
The comparison that comes up most often is a phone book. A phone book lets you look up a person's name and find their number. DNS does the same thing for the internet. You provide the name, and DNS returns the number your browser needs to make the connection.
Without DNS, every website visit would require you to type something like 192.0.2.1 instead of a simple domain name. DNS makes the internet usable for everyone, not just engineers.
How does a DNS lookup work?
Every time you visit a website, a DNS lookup happens in the background. The whole process takes milliseconds, but it involves several steps and multiple servers. Here is how it works from the moment you hit enter in your browser.
Step 1. Your browser checks its cache
Before reaching out to any server, your browser checks whether it already has the IP address saved from a recent visit. If you visited the same site five minutes ago, the answer is probably still stored locally. If it is, the lookup ends here and the page loads immediately.
Step 2. The request goes to a DNS resolver
If the browser does not have the answer cached, it sends the request to a DNS resolver. This is usually a server run by your internet provider. The resolver acts as the middleman. It does not know the answer itself, but it knows where to ask.
Step 3. The resolver contacts a root server
The resolver first contacts one of the internet's root servers. There are 13 sets of root servers spread around the world. The root server does not know the IP address of your domain, but it knows which server handles the domain extension. If you are looking for a .com domain, the root server points the resolver to the .com TLD server.
Step 4. The TLD server responds
TLD stands for top-level domain. The TLD server for .com knows which nameserver is responsible for each .com domain. It does not return the final IP address. Instead, it tells the resolver which authoritative nameserver to contact next. Understanding domain extensions helps explain why this step exists. Each extension has its own set of TLD servers managing the domains beneath it.
Step 5. The authoritative nameserver returns the IP address
The authoritative nameserver is the final stop. This server holds the actual DNS records for your domain, including the IP address where your website lives. It sends the IP address back to the resolver, which passes it to your browser. Your browser then connects to that IP address and loads the site.
The entire chain, from browser to resolver to root server to TLD server to authoritative nameserver and back, typically completes in under 100 milliseconds.
What are nameservers and why do they matter?
Nameservers are the servers that store your domain's DNS records. When you finish registering a domain, one of the first things you configure is which nameservers it should use. Those nameservers tell the rest of the internet where to find your website, where to deliver your email, and how to handle other services connected to your domain.
If your nameservers are set incorrectly, nothing connected to your domain will work. Your website will not load. Your email will not arrive. Any service tied to that domain stops until the nameservers are pointed to the right place.
Most domain registrars provide their own nameservers by default. If your website is hosted elsewhere, you may need to update your nameservers to point to your hosting provider instead. This is a common step when connecting a domain to a website builder or a separate hosting account, and it ties directly into the difference between domain vs hosting.
What happens when DNS settings are wrong?
DNS problems are some of the most frustrating issues a brand can face online because the symptoms look like something else entirely.
- Your website goes down. If the DNS record pointing to your web server is missing or incorrect, browsers cannot find your site. The domain is still yours, but visitors see an error page instead of your content.
- Email stops working. Email relies on a specific type of DNS record called an MX record. If the MX record is deleted, changed, or pointed to the wrong server, emails sent to your domain bounce back or disappear entirely.
- SSL certificates fail. Some SSL verification methods depend on DNS records. If those records are removed or changed during a certificate renewal, the renewal fails and your site loses its secure connection.
- Third-party services break. Many tools that connect to your domain, such as email marketing platforms or analytics verification, require specific DNS records to function. Removing or altering those records disconnects the service.
The fix for most DNS problems is straightforward. Check the records, find the mistake, and correct it. The challenge is knowing which record to look at and what it should say. That is why understanding the basics of DNS records matters, even if you never plan to manage them yourself.
How does DNS propagation work?
When you change a DNS record, the update does not take effect instantly around the world. DNS servers at every level of the lookup chain cache (temporarily save) the previous answer. Until those caches expire and refresh, some visitors will still be sent to the old IP address while others reach the new one.
This process is called DNS propagation. It typically takes anywhere from a few minutes to 48 hours, depending on the TTL (time to live) value set on the record. The TTL tells DNS servers how long to keep the cached answer before checking for a new one.
During propagation, your site may work for some visitors and not for others. This is normal. There is no way to force every DNS server on the internet to update at the same time. The best approach is to plan DNS changes during low-traffic periods and set a shorter TTL before making the change so the old cache expires faster.
Common DNS terms explained
DNS has its own vocabulary. Here are the terms you are most likely to encounter when managing a domain.
- A record. Points a domain name to an IPv4 address (the standard number format like 192.0.2.1). This is the record that connects your domain to the server where your website is hosted.
- CNAME record. Points one domain name to another domain name instead of an IP address. Often used when a subdomain (like www) needs to resolve to the same place as the main domain.
- MX record. Tells the internet which mail server handles email for your domain. Without a correct MX record, email sent to your domain will not be delivered.
- Nameserver (NS record). Specifies which nameservers are authoritative for your domain. This is what you update when you move your domain's DNS management from one provider to another.
- TXT record. Holds text-based information that other services can read. Commonly used for email verification, domain ownership confirmation, and security policies.
- TTL (time to live). A value set on each DNS record that controls how long other servers cache the record before requesting a fresh copy. Shorter TTLs mean faster updates but more frequent lookups.
The next chapter in this series covers DNS records in full detail, including when to use each type and how to configure them correctly.
How WEMASY handles DNS
When you build a site with WEMASY and connect your own domain, WEMASY provides the DNS configuration you need. The platform tells you exactly which records to set and where to point your nameservers. SSL is handled automatically, so you do not need to create separate DNS records for certificate verification.
For brands that want to keep DNS management simple, WEMASY reduces the setup to a few steps. You register your domain, update the records as guided, and the platform takes care of the connection between your domain and your live site. See what is included across plans at WEMASY pricing.
Frequently asked questions about DNS
Can DNS affect how fast your website loads?
Yes. The speed of the DNS lookup is the first step in loading any web page. If your DNS provider is slow or if DNS records are not configured efficiently, the lookup takes longer and delays the start of the page load. Choosing a reliable DNS provider with servers spread across multiple regions helps keep lookup times short for visitors everywhere. With WEMASY's website builder, you can set this up directly on your website.
Is it possible to use different DNS providers for the same domain?
Technically, you can point a domain to nameservers from two different providers, but this is not recommended for most brands. Both providers need to have identical DNS records at all times, and keeping them in sync adds complexity. For most sites, using one DNS provider and keeping all records in one place is simpler and less prone to errors.
What is the difference between DNS and a URL?
A URL is the full address you see in your browser, including the protocol (like https), the domain name, and the specific page path. DNS only handles the domain name portion. When your browser reads a URL, it extracts the domain name and uses DNS to convert that name into the IP address of the server. The rest of the URL tells the server which specific page or file to deliver.
Can you change DNS records without changing your domain registrar?
Yes. DNS management and domain registration are separate functions. You can keep your domain registered with one provider while pointing its nameservers to a completely different DNS provider. This is common when a brand registers a domain at one company but hosts its website with another. Updating the nameserver settings at your registrar is all that is needed to make the switch.
What happens to DNS records if your domain expires?
When a domain expires, the DNS records associated with it stop working. The domain enters a grace period where the registrar may still hold the records, but they are no longer served to the internet. If the domain is not renewed during the grace period, it eventually becomes available for anyone to register, and all previous DNS records are lost permanently. Keeping your domain renewed and your registration details current prevents this from happening.