What is a nameserver?

If you have read the chapter on what DNS is, you know that the Domain Name System translates domain names into IP addresses. Nameservers are the specific servers within that system that store the instructions for your domain. Every time someone types your domain into a browser, the DNS lookup ends at a nameserver. That nameserver looks up the right records and sends the visitor to your website.

What is a nameserver?

A nameserver is a server that stores DNS records for a domain name. Those records contain the information that connects your domain to your website, your email, and any other service tied to it. When a browser asks "where does this domain live?", the nameserver is the one that answers.

Think of it like a directory at a large office building. The building has hundreds of offices, and each one has a different tenant. The directory in the lobby tells you which floor and room number to go to. A nameserver does the same job for the internet. It tells browsers and email servers exactly which server to visit for a given domain.

Every domain that works on the internet has nameservers assigned to it. If a domain has no nameservers, nothing happens when someone tries to visit it. No website loads, no email gets delivered, and no services connect.

How do nameservers connect to DNS?

Nameservers are a specific type of DNS server. They are the authoritative servers for your domain, meaning they hold the final, correct version of your domain's settings. When a DNS lookup reaches the nameserver, the nameserver gives the definitive answer about where your domain points.

During a typical DNS lookup, several servers get involved. The browser contacts a resolver, which contacts root servers, which point to TLD servers, which point to your nameserver. Your nameserver is the last stop. It looks up the matching record and returns the result. That is why nameservers are called "authoritative." They do not guess or cache. They hold the source of truth for your domain.

What do nameserver addresses look like?

Nameserver addresses are formatted as domain names themselves. They usually follow a pattern like this.

• ns1.example.com
• ns2.example.com

The "ns" stands for nameserver. The number after it (ns1, ns2, ns3) tells you which one in the set it is. Some providers use different naming patterns, but the structure is always a subdomain that identifies it as a nameserver. Here are a few real-world examples of what domain nameservers look like.

• ns1.hostingprovider.com and ns2.hostingprovider.com
• dns1.registrar.com and dns2.registrar.com
• a.ns.provider.net and b.ns.provider.net

Your registrar or hosting provider gives you these addresses when you sign up. You can also look them up in your domain account or through a WHOIS search.

Why are there always at least two nameservers?

Every domain is required to have at least two nameservers. The reason is redundancy. If one nameserver goes down or becomes unreachable, the second one takes over and keeps your domain working. Without a backup, a single server outage could take your entire website and email offline.

Most providers assign two nameservers by default. Some assign three or four for extra reliability. All of them hold the same information, and the internet can query any one of them to get the right answer for your domain.

Where do you find your nameservers?

Your current nameservers are listed in your domain registrar account. Log in to the registrar where you bought your domain and look for the DNS settings or nameserver section. The exact location varies between providers, but it is usually under domain management or domain settings.

You can also find your nameservers without logging in by running a WHOIS lookup on your domain. The results will show the nameserver entries along with other registration details.

When do you need to change your nameservers?

Most of the time, your nameservers stay the same. But there are a few situations where you need to update them.

• You are moving your website to a new hosting provider that uses its own nameservers
• You are switching to a third-party DNS provider for better speed or features
• You are setting up a CDN (content delivery network) that requires its own nameservers
• You are pointing a domain to a website for the first time and the hosting provider tells you to use their nameservers

If your registrar and hosting provider are the same company, you may never need to touch your nameservers. They are already set to the right ones. Changes are only needed when you want your domain's DNS handled by a different provider than your registrar.

How do you change nameservers?

Changing nameservers is straightforward. The steps are the same regardless of which registrar you use.

Step 1. Get the new nameserver addresses

Your new hosting or DNS provider will give you the nameserver addresses you need. These are usually listed in their setup guide or welcome email. Copy them exactly as provided.

Step 2. Log in to your registrar

Go to the registrar where your domain is registered. This is not always the same company as your hosting provider. If you are unsure which registrar holds your domain, run a WHOIS lookup and check the registrar field.

Step 3. Find the nameserver settings

Look for a section called nameservers, DNS settings, or domain management. Some registrars label it "custom nameservers" or "change nameservers."

Step 4. Replace the old nameservers with the new ones

Delete the existing nameserver entries and paste in the new ones. Make sure you enter at least two. Save the changes.

Step 5. Wait for propagation

After saving, the update needs to spread across the internet. This process is called DNS propagation. It can take anywhere from a few minutes to 48 hours, though most changes take effect within a few hours.

What happens after you change nameservers?

Once you change your nameservers, the internet gradually picks up the new settings. During propagation, some visitors may still see the old site while others see the new one. This is normal and temporary.

There is a small chance of temporary downtime during the switch. If your DNS records are not set up at the new nameserver before you make the switch, visitors may see an error page until those records are in place. The best way to avoid this is to configure all your DNS records at the new provider before changing the nameservers at your registrar.

What is the difference between a nameserver and a DNS server?

A nameserver is a type of DNS server. The term "DNS server" is broader. It includes resolvers, root servers, TLD servers, and nameservers. A nameserver specifically refers to the authoritative server that holds the final DNS records for a domain.

When people say "DNS server" in everyday conversation, they often mean the resolver (the server that looks up the answer for you). When they say "nameserver," they mean the server that holds the answer. Both are part of the DNS system, but they play different roles in the lookup process.

What is the difference between default and custom nameservers?

When you register a domain, your registrar automatically assigns its own nameservers. These are called default nameservers. They work fine for managing your DNS records directly through your registrar's control panel.

Custom nameservers are nameservers from a different provider. You might switch to custom nameservers when you move your hosting, use a CDN, or switch to a dedicated DNS provider that offers faster lookup times or more advanced features. Changing to custom nameservers means your registrar no longer controls your DNS records. The new nameserver provider takes over that role instead.

How WEMASY handles nameservers

When you build a website on WEMASY and connect your own domain, WEMASY provides the nameserver addresses you need. You enter them in your registrar account, and once propagation finishes, your domain points to your WEMASY site. WEMASY manages hosting, SSL, and DNS records from there, so you do not need to configure individual records yourself. See what is included in each plan on the WEMASY pricing page.

What comes next

Now that you understand what nameservers are and how to change them, the next step is learning about the individual records that nameservers store. Each record type handles a different job, from sending visitors to your website to routing your email. The next chapter covers DNS records and what each type does.

FAQ