You own a domain. You want your website to load from a new host. The bridge between these two is the nameserver. Most people mess this up because they treat it like a magic switch. It is not. It is a delegation of authority. If you get the order wrong, your site goes dark. Your email stops. Your SSL certificates break. This guide walks you through the eight specific moves required to change nameservers without breaking anything. We assume you have zero prior knowledge. We will define every term and give you the exact commands to verify your work.
What Is a Nameserver?
Think of the internet as a massive phone book. Your domain name (like example.com) is the name in the book. The IP address (like 93.184.216.34) is the phone number. But the phone book is split into smaller sections. A nameserver is the authority that says, "I own the section for example.com. Ask me for the phone numbers."
When you buy a domain, the registrar (GoDaddy, Namecheap, Cloudflare, etc.) points to two or more nameservers. These nameservers tell the world where to find your DNS records. When you move hosting, you often keep the domain at the same registrar but change the nameservers to point to your new host. This is the "change nameserver" action.
Move 1: Locate Your Registrar
You cannot change nameservers if you do not know who holds your domain. Log in to the service where you bought the domain. Look for a section labeled "DNS Management," "Domain Settings," or "Nameservers." If you use Cloudflare as your registrar, the interface is called "DNS" but the nameserver change happens in the "Domain" settings. If you use a dedicated domain registrar, it is usually under "Advanced DNS" or "Domain Settings."
Do not confuse the registrar with the hosting provider. Your host (the server company) does not control the domain name. They only control the data on the server. The registrar controls the pointer.
Move 2: Get the New Nameserver Strings
Contact your new hosting provider. Ask for their nameserver strings. They will give you two or more addresses. They look like this:
ns1.yourhost.com
ns2.yourhost.com
Sometimes they provide four. Sometimes they provide custom ones like dns1.dynadot.com. Copy them exactly. Typos here are fatal. If you miss a dot, the DNS lookup fails. If you add a trailing dot, some resolvers fail. Copy-paste from the host's dashboard if possible.
Move 3: Verify Current DNS Records
Before you break anything, you need a snapshot of your current state. If your website is live, you have DNS records (A records, MX records, CNAMEs). When you change nameservers, you are telling the world to stop listening to the old host and start listening to the new one.
If your new host does not have these records imported, your site will die. Ask your new host: "Do you have my DNS records imported?" If they have not imported them, your site will show an error page. Check your current records using dig or nslookup.
dig example.com A
dig example.com MX
Note the IP addresses and mail servers. You will need these to verify the new setup later.
Move 4: Check TTL Values
TTL stands for Time To Live. It is the number of seconds that DNS resolvers (like your ISP or Google) cache the record. If your TTL is 86400 (24 hours), it could take a full day for the change to propagate globally.
If you are about to change nameservers, lower your TTL first. Log in to your current host's DNS panel. Find the A record and MX record. Change the TTL to 300 or 600 seconds. Wait for the current TTL to expire. How do you know it expired? Check it.
dig example.com A +noall +answer +ttl
Look at the TTL number. When it drops below 600, you are safe to proceed. If you skip this step, you might wait 24 hours for the change to take effect, and users might see the old site or the new site randomly. This is called "split brain." It is confusing and looks bad.
Move 5: Update the Nameservers at the Registrar
Now you are ready. Go to your registrar's panel. Delete the old nameservers. Add the new ones. Save the change.
Some registrars require you to enter all nameservers at once. Others let you add one at a time. If you can add one at a time, add the first new nameserver, save, then add the second. This ensures you always have at least two active nameservers. Never leave a domain with zero nameservers. That is a DDoS waiting to happen.
After saving, the registrar will update the zone file. This takes a few minutes. You will not see a confirmation email immediately. The change is not instant.
Move 6: Verify Propagation
How do you know the change worked? You check from different locations. DNS propagation is not binary. It is gradual. Some resolvers see the new nameservers immediately. Others see the old ones for hours.
Use an online tool like dnschecker.org or whatsmydns.net. Enter your domain. Look at the "NS" section. You will see a list of countries and ISPs. If most show the new nameservers, you are good. If some show the old ones, wait.
You can also check locally. On your server, run:
dig NS example.com
If the output shows the new nameservers, your local resolver has updated. If it shows the old ones, your local cache is still holding the old data. Flush your local DNS cache if you are on Windows (ipconfig /flushdns) or Mac (sudo dscacheutil -flushcache). Do not restart your computer. That is overkill.
Move 7: Confirm DNS Records Are Live
Changing nameservers does not automatically copy your DNS records. If your new host did not import your old records, your site is down.
Check the A record. It should point to your new server's IP. Check the MX records. They should point to your mail server. If the MX record points to the old host, your email will bounce.
Run this command:
dig example.com A
dig example.com MX
Compare the results to what you noted in Move 3. If the A record points to the new IP, your site should load. If the MX record is missing or wrong, fix it immediately. Email is not a "nice to have." It is critical for password resets and notifications.
Move 8: Monitor and Rollback
Keep an eye on your website for 24-48 hours. Check the SSL certificate. If your certificate is tied to the domain, it should still work. If you use a shared IP, the certificate might be different. Test your site in a private browser window to avoid cache issues.
If something breaks, you can roll back. Go to your registrar. Change the nameservers back to the old ones. The old records are still there (assuming you did not delete them). The change will propagate again. This is why you lower the TTL first. A fast TTL means a fast rollback.
Common Pitfalls
Forgetting to Import DNS Records
This is the #1 cause of downtime. You change the nameservers, but the new host has no idea what your A record is. Your site shows a "404 Not Found" or a "Domain Not Found" page.
Fix: Log in to your new host's DNS panel. Add the A record pointing to your server's IP. Add the MX records for email. Add any CNAMEs you need. Save. Wait for propagation.
Using Only One Nameserver
Never use only one nameserver. If that server goes down, your domain becomes unresolvable. Always use at least two. Most hosts provide two or more. If you only have one, contact your host and ask for a second one.
Changing Nameservers at the Host Instead of the Registrar
You cannot change nameservers in your hosting panel. The hosting panel controls the DNS records for the domain, but it does not control the nameserver delegation. That is the registrar's job. If you try to change it in the host panel, you will not see the option.
Ignoring Propagation Time
You change the nameservers, and your site still shows the old content. You panic. You think it is broken. It is not. It is propagating. Wait. Check from a different network (use your phone's mobile data). If the mobile data shows the new site, the change is working. Your home network is just slow to update.
What to Check First
If your site is down after changing nameservers, check these in order:
- Registrar Panel: Did you save the change? Do you see the new nameservers listed?
- DNS Records: Does the new host have the correct A and MX records?
- TTL: Is the TTL low enough? If it is high, wait.
- Local Cache: Did you flush your local DNS cache?
- SSL Certificate: Is the certificate valid for the domain?
If all of these are correct, wait. Propagation takes time. Do not change the nameservers again. That resets the clock and makes the problem worse. Be patient. Check from multiple locations. If it still fails after 48 hours, contact your registrar and host with the dig outputs you gathered. They will need that data to troubleshoot.
FAQ
How long does it take to change nameservers?
The change at the registrar takes minutes. Propagation takes 24-48 hours globally. If you lowered the TTL first, it might take only a few hours.
Can I change nameservers without affecting my website?
Yes, if you import your DNS records to the new host first. If you do not, your website will go down until you add the records manually.
What if my email stops working?
Check the MX records. If they point to the old host, email will bounce. Update the MX records in the new host's DNS panel to point to the correct mail server.
Do I need to change nameservers if I keep the same host?
No. If you stay with the same host, your nameservers remain the same. You only change nameservers when you move to a new host or a new DNS provider.