Article Contents
- 1 Key Takeaways
- 2 What Name Servers Actually Are
- 3 How Name Servers Fit Into the DNS Resolution Process
- 4 The Difference Between Name Servers and DNS Records
- 5 Where Name Servers Are Managed
- 6 When You Should Change Your Name Servers
- 7 How To Change Your Name Servers Step by Step
- 8 DNS Propagation After Changing Name Servers
- 9 Mistakes To Avoid When Changing Name Servers
- 10 How To Verify Your New Name Servers Are Working
- 11 Get Your Name Servers and DNS Updated Without Downtime
- 12 References & Additional Resources
- 13 Tagged In:
Key Takeaways
- Name servers tell the internet which DNS provider is authoritative for your domain
- DNS records (A, CNAME, MX, TXT, and more) live on the authoritative DNS provider, not at the name server setting itself
- Changing name servers switches DNS providers, so the old provider’s DNS records stop being used once resolvers pick up the new delegation
- If you are only moving web hosting, you often do not need to change name servers, you can usually update A and CNAME records instead
- Name server changes are made at the domain registrar because the registrar publishes delegation information through the registry layer
- The safest workflow is prep first (recreate records at the new DNS host), switch second (update name servers), verify third (confirm NS and key records)
- Propagation after a name server change is driven by caching of delegation data, so some users may hit the old DNS host while others hit the new one
- Keep the old DNS zone intact during propagation to prevent outages, especially for email records like MX, SPF, DKIM, and DMARC
- Verification is simple: confirm the new name servers are saved at the registrar, then use dig or nslookup to confirm NS answers and validate key records
Name servers are one of those “sounds scary, is actually simple” web concepts. If you have ever moved to a new host, turned on Cloudflare, or connected a domain to anything, you have touched name servers. They are the switch that tells the internet which DNS provider is authoritative for your domain.
Here is the mental model that makes everything click. Your domain registrar is where you control the domain registration and update delegation settings like name servers. Your DNS host is where your DNS records live. Your web hosting is where your website files and databases live. Name servers are how your domain points at the DNS host so resolvers can find the records that route traffic to your website, email, and services.
This guide explains what name servers are, how they fit into DNS resolution, when you should change them, and how to do it without breaking your site. Along the way, you will also see the safer alternative when you do not need to change name servers at all, and you only need to update records instead.
What Name Servers Actually Are
Name servers are DNS servers that answer authoritatively for your domain. When a resolver needs records for your domain, it follows the delegation chain until it reaches the name servers listed for that domain, then it asks those servers for the records (A, CNAME, MX, TXT, and more). If you want the standards-level foundation for this delegation model, STD 13 is the DNS standard that includes RFC 1034 and RFC 1035.
The key detail most people miss. Name servers are not “the records.” They are the destination where records are stored. That is why changing name servers is a big change. You are switching which DNS provider is authoritative for the whole domain.
If you want the full DNS refresher first, start with what DNS is and how it works.
How Name Servers Fit Into the DNS Resolution Process
When someone types your domain into a browser, their device asks a recursive resolver to find the answer. If it is not cached, the resolver follows the DNS hierarchy and ends up at the authoritative name servers for your domain. Those name servers return the records the browser needs to connect to your site.
Practically, this means one mistake at the name server layer can make everything look broken. Website down. Email failing. Verification checks not working. Not because your hosting changed, but because the internet no longer knows where your DNS records live.
If you want the hands-on version of how DNS and hosting connect, this walkthrough on connecting domain and hosting is the cleanest place to start.
The Difference Between Name Servers and DNS Records
This is the decision point that prevents most migrations from going sideways:
Changing name servers means switching your DNS provider. After the change, the old provider’s DNS records stop being used.
Editing DNS records means you keep the same DNS provider, and you only change the instructions inside it.
So if you are moving your website to a new host but you want to keep DNS where it is, you often do not need to change name servers at all. You update your A record or CNAME to point to the new host. That workflow is covered in how to point a domain to a web host.
If you want a broader explanation of how these layers split up, domain hosting vs web hosting makes the “who does what” feel obvious.
Where Name Servers Are Managed
Name servers are usually set at your domain registrar, not inside your hosting account. That is why switching DNS providers starts in your registrar dashboard, even if your DNS provider gives you the new name servers.
If the registrar piece is still fuzzy, this guide to domain registrars makes the roles clear fast.
When You Should Change Your Name Servers
You should change name servers when you are intentionally moving DNS hosting to a different provider, for example:
- Switching from registrar DNS to a dedicated DNS platform
- Turning on a service that requires you to use the provider’s assigned name servers (Cloudflare is a classic example)
- Moving DNS management to your web host because you want everything in one dashboard
You usually do not need to change name servers just because you changed web hosts. In many migrations, you keep DNS where it is and update A and CNAME records to the new host.
How To Change Your Name Servers Step by Step
Before you touch anything, do this one thing: make sure your DNS zone is fully set up at the new DNS provider. Copy over every record you need (website, www, email, verification, anything else). If you skip this, your domain will “switch” successfully and then resolve to nothing.
Then follow this process:
- Step 1: Get the new name servers from your DNS provider (usually two, sometimes more)
- Step 2: Log in to your registrar and open the domain’s name server settings
- Step 3: Choose custom name servers, paste them exactly as provided, save
- Step 4: Keep your old DNS provider’s zone intact during propagation (do not delete it yet)
- Step 5: Verify NS and key records, then clean up later when you are confident everything is stable
If you want a real-world example of the “prep, change, verify” flow inside a major DNS platform, Cloudflare’s full setup guide walks through reviewing records, changing name servers at the registrar, and validating the change.
DNS Propagation After Changing Name Servers
Propagation is the transition period where different resolvers may still be using cached delegation data. During this window, some users may resolve your domain using the old DNS provider, others using the new one.
The practical rule: do not remove DNS records from the old provider immediately. Leave both zones working until you are confident traffic has fully shifted and email is stable.
Mistakes To Avoid When Changing Name Servers
- Switching name servers before recreating DNS records at the new provider
- Typos in name servers, or pasting only one of them
- Mixing name servers from different providers (this can create inconsistent or broken authoritative answers)
- Forgetting email records (MX, SPF, DKIM, DMARC) and wondering why mail stopped
If you want a broader view of the DNS layer that name servers sit inside, this DNS guide pairs well with troubleshooting and checklists.
How To Verify Your New Name Servers Are Working
You can verify in three practical ways:
- Check the registrar panel to confirm the new name servers are saved
- Use dig or nslookup to check NS records and confirm the authoritative source
- Confirm key records resolve correctly (A or CNAME for the website, MX and TXT for email)
If the authoritative answers are coming from the new provider and your key records match what you expect, you are in good shape.
If you are still deciding whether your hosting provider should also be your DNS provider, this breakdown of what a web host does helps you compare “all-in-one” hosting dashboards vs keeping DNS separate.
Get Your Name Servers and DNS Updated Without Downtime
If you are ready to make changes with confidence, Web Hosting Services can help you map out the safest path for name server updates, DNS record changes, and hosting moves without the usual “why is everything broken” moment. Whether you are switching DNS providers, moving to a new web host, or enabling a platform like Cloudflare, the goal is the same: reliable routing, stable email, and a setup you can adjust later without chaos.
Need a second set of eyes on your DNS records, propagation timing, or the best way to connect your domain to your hosting plan. Contact us and we will help you get it sorted.
References & Additional Resources
- RFC Editor. STD 13, Domain Name System (includes RFC 1034 and RFC 1035). https://www.rfc-editor.org/info/std13
- ICANN. Domain Name System resources. https://www.icann.org/resources/pages/dns-2022-09-13-en
- Mozilla MDN Web Docs. DNS glossary. https://developer.mozilla.org/en-US/docs/Glossary/DNS
- Cloudflare Developer Docs. DNS. https://developers.cloudflare.com/dns/
- Cloudflare Developer Docs. Set up a primary zone (Full setup), including changing nameservers and verifying changes. https://developers.cloudflare.com/dns/zone-setups/full-setup/setup/
- ICANN. Registrar Accreditation Agreement. https://www.icann.org/en/contracted-parties/accredited-registrars/registrar-accreditation-agreement
Disclaimer: This content is for informational purposes only and does not constitute technical support or professional advice. DNS providers, registrars, interfaces, and name server requirements can change without notice. Always confirm the correct name servers and DNS records directly with your registrar and DNS provider before making changes. DNS and name server updates can cause temporary routing differences due to caching and propagation, and mistakes can interrupt website and email delivery. If your domain or email is business critical, consider testing changes on a staging domain or consulting a qualified professional.
I am a web hosting specialist with over 15 years of experience in digital marketing, web design, and website and hosting management. My background includes managing and maintaining websites for clients across a wide range of industries, with a long-standing focus on building and supporting search engine optimization friendly websites.
My work sits at the intersection of hosting infrastructure, website performance, and real-world usability. Over the years, I’ve worked extensively with hosting environments, domain systems, DNS configuration, and server platforms while also designing and managing websites that need to perform reliably in search results, under traffic, and over time.
This site exists to explain web hosting clearly and accurately, based on research and hands-on experience rather than marketing claims.
