You have hosting with provider A and your domain with provider B. Or you're moving to new hosting. In both cases you need to change the nameservers so your domain points to the right server.

What are nameservers?

Nameservers are the servers that hold your domain's DNS information. They tell the internet where your website and email can be found.

Every hosting provider has its own nameservers, for example:

  • ns.theory7.net, ns.theory7.eu, ns.theory7.nl
  • ns1.provider.com / ns2.provider.com

You always have at least two nameservers (for redundancy).

When do you need to change nameservers?

  • New hosting: Your domain needs to point to your new host
  • Domain registered elsewhere: Domain with registrar A, hosting with B
  • Using a CDN: Cloudflare requires their nameservers
  • Moving: From an old to a new hosting provider

Where do you change nameservers?

You change nameservers at your domain registrar — that's where you bought the domain. This can be a different party than your hosting provider.

Not sure where your domain is registered? Do a WHOIS lookup to find the registrar.

Changing nameservers step by step

Step 1: Note the new nameservers

Ask your (new) hosting provider which nameservers to use. This is usually in the welcome email or the customer portal.

Step 2: Log in to your domain registrar

Go to the website where you registered your domain and log in.

Step 3: Go to DNS/nameserver settings

Look for:

  • "DNS management"
  • "Nameservers"
  • "Domain settings"

Step 4: Change the nameservers

  1. Remove the current nameservers
  2. Enter the new nameservers (at least 2)
  3. Save

Step 5: Wait for propagation

DNS changes spread across the entire internet. This usually takes 1-24 hours, sometimes up to 48 hours.

Speeding up propagation

You can't really speed up propagation, but you can prepare:

  • Lower the TTL (Time To Live) to 300 seconds a day in advance
  • Set everything up on the new hosting before you change the nameservers
  • Test with your hosts file to check whether the new server works

Checking if it worked

After a few hours you can check:

  • whatsmydns.net: Check DNS propagation worldwide
  • Command line: nslookup yourdomain.com
  • Browser: Open your site (watch out for caching!)

Risks and things to watch for

Email interruption

If your email was on the old server, it stops working after the change. Make sure email is configured on the new server before you change nameservers.

Website temporarily offline

During propagation some visitors may see your old server, others the new one. This is normal.

Incorrect nameservers

Typos in nameservers = site offline. Double-check before you save.

Frequently asked questions

Will I lose my email when I change nameservers?

Not if your email is correctly configured on the new server. Emails during propagation may arrive with some delay.

Can I mix nameservers from different providers?

Technically yes, but it's not recommended. Use the nameservers of a single provider.

What if I accidentally enter the wrong nameservers?

Change them back. It just takes a while again for the correction to take effect.

Nameservers for Theory7

Changing nameservers step by step

Step 1: look up the new nameservers

You'll find your hosting provider's nameservers in:

  • The welcome message with your hosting plan
  • Your hosting panel under DNS or Domains
  • Your provider's documentation or FAQ

Nameservers look like this: ns1.provider.com and ns2.provider.com. You need at least two.

Step 2: log in to your registrar

Go to the website where your domain is registered. This is your registrar — not to be confused with your hosting provider (they can be different).

Step 3: change the nameservers

Look in your dashboard for "DNS" or "Nameservers". Replace the current nameservers with the new ones. Save.

Step 4: wait for propagation

DNS changes take time to roll out globally (propagation). This usually takes 1-24 hours, sometimes up to 48 hours. During this period your domain may work inconsistently.

Nameservers vs DNS records

There are two ways to connect your domain:

Changing nameservers

You hand over full control of DNS to your hosting provider. They manage all DNS records. Simpler, but you can't manage records at your registrar.

Changing the A record

You keep your nameservers with your registrar and only change the A record to your hosting's IP. You keep control but need to set up more manually.

For most situations, changing nameservers is the easiest option.

Common problems

Website doesn't work after the change

DNS propagation can take up to 48 hours. Wait first. Check with whatsmydns.net whether the new nameservers are already active.

Email stops working

If your email is with a different provider, the MX records need to be set correctly at your new nameservers. Check this in your hosting panel.

Wrong nameservers entered

No panic — correct the nameservers and wait for propagation. Nothing is permanently broken.

Going back to the old nameservers

Want to go back to your old hosting? Change the nameservers back. That's why you should always note your old nameservers before changing them.

Nameservers and Cloudflare

If you use Cloudflare, you point your nameservers to Cloudflare (not to your hosting). Cloudflare then manages your DNS and routes traffic to your server. This provides extra features like CDN and DDoS protection.

Here are the nameservers of commonly used services:

Cloudflare

You get unique nameservers assigned when adding your domain, such as name.ns.cloudflare.com.

Major hosting providers

Every provider has its own nameservers. You'll find them in:

  • The welcome message with your hosting plan
  • Your hosting dashboard
  • The knowledge base/documentation

Nameserver troubleshooting

Check current nameservers

Use tools like whatsmydns.net or nslookup to see which nameservers are active.

Checking propagation

After a change you can follow progress via whatsmydns.net. Green checkmarks mean the new nameservers are already active there.

Common causes of problems

  • Typos in the nameservers
  • Nameservers not fully filled in (at least 2 needed)
  • Change not yet saved at the registrar
  • Propagation not yet complete (wait 24-48 hours)

Changing nameservers is a standard procedure that happens millions of times a day. With the right information and a bit of patience for propagation, it almost always goes smoothly.

Nameservers are the link between your domain name and your hosting server. They tell the internet where your website lives. Changing nameservers is often needed when moving hosting or when setting up services like Cloudflare.

Keep in mind that nameserver changes need time to take effect worldwide — this is called DNS propagation. During this period your website may be temporarily unreachable or switch between the old and new server. This is normal and resolves itself.

Always note your current nameservers before changing them. If something goes wrong, you can set them back. And check after the change that your website, email, and other services still work correctly. A careful approach prevents unnecessary downtime.

Nameservers form the bridge between your domain and your hosting. Setting them up correctly is essential for a working website. Take your time, follow your hosting provider's instructions carefully, and patiently wait until DNS propagation is complete. Within a day everything is rolled out and your website works at the new location.

Take your time when changing nameservers. A correct configuration prevents downtime and ensures a smooth transition to your new hosting environment. Always wait for full propagation before you test.

Take your time with nameserver changes. Patience is rewarded with a smooth transition without interruptions for your visitors.

At Theory7 hosting you use our nameservers. You'll find these in your welcome email or customer portal. Need help setting it up? Our support team is happy to help.

Changing nameservers: overview per registrar

RegistrarChange nameservers viaTurnaround time
TransIPControl panel > Domain names > Change nameservers0-24 hours
VersioMy Account > DNS > Change nameservers0-24 hours
AntagonistCustomer panel > Domain > Change nameservers0-48 hours
HostnetMy Hostnet > Domain > Change nameservers0-24 hours

Changing nameservers works in a similar way at most registrars.

Changing nameservers: step-by-step per provider

Changing nameservers differs per domain registrar. Below you'll find the steps for the most popular providers in the Netherlands.

Changing nameservers with SIDN (.nl domains)

For .nl domains you manage the nameservers through your registrar, not directly with SIDN. Log in to your registrar (for example TransIP, Versio, or Theory7), go to domain management, find the DNS or nameserver settings, and replace the current nameservers with the new ones. SIDN usually processes the change within a few hours, but full DNS propagation can take up to 24 hours.

Common mistakes when changing nameservers

  • Typos in nameserver addresses – Always copy and paste the exact nameserver addresses from your new provider
  • Not changing all nameservers – Always replace all nameservers at once, not just one
  • DNS records not prepared – Create all needed DNS records at the new nameserver provider first
  • Forgetting email – Check that MX records are set correctly at the new nameservers
  • Testing too early – Wait at least two hours before drawing conclusions about the change

Changing nameservers: advanced configurations

Besides simply changing nameservers, there are advanced configurations you can apply for better performance and security.

Enabling DNSSEC

After changing your nameservers it's a good idea to enable DNSSEC. DNSSEC adds a cryptographic layer to your DNS records, so they can't be forged. This protects your visitors against DNS spoofing attacks. Note: if you switch providers, DNSSEC needs to be reconfigured at the new provider. Disable DNSSEC at the old provider first, change the nameservers, and then enable it again at the new provider.

Secondary nameservers and redundancy

Always use at least two nameservers for redundancy. If one nameserver goes offline, the other takes over. Many providers offer three or four nameservers for even better availability. For business-critical websites you might consider using an external DNS provider like Cloudflare or Route53 alongside your hosting provider's nameservers. This offers extra protection against DDoS attacks at the DNS level.

Nameservers and website performance

The location and speed of your nameservers indirectly affect how fast your website loads. Nameservers closer to your visitors respond faster to DNS queries. A DNS provider with an anycast network (like Cloudflare) automatically routes DNS requests to the nearest server. This can cut DNS resolution time in half. Combine fast nameservers with good website speed optimization for the best result.

When should you change nameservers?

There are several situations in which changing nameservers is necessary or desirable.

When moving your website

If you move your website to a different hosting provider, you need to change the nameservers to those of your new provider. Plan this carefully: first fully set up your website with the new host, test everything thoroughly, and only then change the nameservers. This minimizes downtime during the switch.

When using a CDN or DNS service

When you want to use a CDN like Cloudflare, you need to change your nameservers to Cloudflare's. Cloudflare then acts as a proxy between your visitors and your server, which provides better performance, DDoS protection, and extra security features. After the nameserver change, you manage your DNS records through the Cloudflare dashboard instead of your hosting provider.

Changing nameservers: checklist

Use this checklist when changing nameservers to guarantee a smooth transition. Before the change, note all current DNS records (A, AAAA, MX, CNAME, TXT, SPF, DKIM). Create these records at the new nameserver provider. Lower the TTL of all records to 300 seconds, at least 48 hours before the planned change. Check that your email is configured correctly at the new provider. Perform the nameserver change and monitor propagation via whatsmydns.com. After the change, test your website, email, and any subdomains. Only after confirming everything works should you set the TTL values back to the default (3600 seconds). Keep the old DNS configuration available for at least a week as a reference in case corrections are needed.

Changing nameservers: understanding DNS propagation

After changing nameservers it takes some time before the change is rolled out worldwide. This process is called DNS propagation and can take up to 48 hours, although it's usually complete within 2 to 6 hours. During propagation some visitors may still reach the old server while others already land on the new server. This is normal and unavoidable. Propagation speed is influenced by the TTL values of your old records, caching by ISPs' DNS resolvers, and the visitor's geographic location. By lowering the TTL to 300 seconds beforehand, you significantly shorten the propagation time. Use tools like whatsmydns.com to monitor propagation progress in real time from different locations worldwide.

Changing nameservers: summary

Changing nameservers is an essential but relatively simple procedure that every website administrator should master. The key points summarized: prepare the change by documenting DNS records and lowering the TTL. Create all records at the new provider before you switch. Perform the change and monitor propagation. Test your website, email, and subdomains after the change. Keep the old configuration as a reference. With the right preparation, a nameserver change goes smoothly without downtime or issues. If in doubt, you can always contact your hosting provider for help with the change process.

Changing nameservers with Theory7

At Theory7, once you set up your hosting account you automatically receive the correct nameservers to set at your domain registrar. Our nameservers run on an anycast network for maximum speed and availability. After changing your nameservers, your DNS records are manageable through the Theory7 dashboard. Our Dutch customer service is happy to help you correctly set up your nameservers and DNS records if you need assistance.

Changing nameservers: configuring DNS records

After changing nameservers you need to correctly set up all DNS records at your new provider. The most important records are: the A record (links your domain to your server's IP address), CNAME record (creates an alias from a subdomain to another domain), MX records (routes email to the right mail server with priority), TXT records (for SPF, DKIM, and DMARC email verification), and AAAA record (for IPv6 addresses). Document all current DNS records before changing the nameservers. After the change, check with a DNS lookup tool that all records resolve correctly. Don't forget the TTL values: use 300 seconds during migration and increase to 3600 or higher after successful verification.

Changing nameservers: frequently asked questions

We answer the most common questions about changing nameservers here. How long does propagation take? Usually a few hours, up to 48 hours maximum for worldwide propagation. Can my website go offline? Not if you've correctly set up the DNS records at the new provider before switching. Does it affect my email? Yes, make sure the MX records are set correctly at the new nameservers. Do I need to disable DNSSEC? Yes, deactivate DNSSEC at the old provider before changing the nameservers, otherwise your domain may become unreachable. Can I undo the change? Yes, you can set the old nameservers again, but keep propagation time in mind.

Changing nameservers: monitoring after the change

After changing nameservers, active monitoring is essential. Use DNS Checker (dnschecker.org) to check propagation status worldwide. Verify that your website loads correctly in multiple browsers and on mobile devices. Test sending and receiving email with external addresses. Check that all subdomains resolve correctly to the right servers. Monitor your website uptime with a tool like UptimeRobot that alerts you to downtime. Keep an eye on Google Search Console for any crawl errors or indexing issues in the days after the change. If everything works correctly after 48 hours, you can raise the TTL values back to the default of 3600 seconds or higher for better caching performance.

With the knowledge from this article you're fully prepared to change your domain's nameservers without downtime or problems. Prepare the change, document all DNS records, test after propagation, and monitor actively. If in doubt, you can always contact your hosting provider's customer service for expert guidance through the change process.

Free tool: Use our DNS Lookup tool. View all DNS records of a domain: A, AAAA, MX, TXT, NS, and more.