What Are Nameservers and How to Change Them

Every time someone types your domain name into a browser, a quiet but critical lookup happens behind the scenes. Before a single byte of your website loads, the internet needs to figure out which server to talk to. That job belongs to nameservers. If you have ever moved a website to a new host, pointed a domain to Cloudflare, or just bought a domain and wondered what to do next, understanding nameservers is the single most important piece of DNS knowledge you can have. This guide explains what nameservers are, how they work, and gives you exact step-by-step instructions for changing them at the most popular domain registrars.

What Nameservers Actually Do

A nameserver is a specialized DNS server that holds the authoritative DNS records for a domain. When someone resolves your domain, their device asks a recursive resolver (usually provided by their ISP or a public DNS service like 8.8.8.8) to find the IP address. That resolver eventually reaches the root DNS servers, which point it to the Top-Level Domain (TLD) nameservers for your extension (.com, .net, .org, etc.). Those TLD nameservers then say: "For example.com, go ask these nameservers" — and they return your nameservers specifically.

Your nameservers are where the buck stops. They hold the actual DNS zone file: the A records, MX records, CNAME records, TXT records, and everything else that tells the internet how to handle traffic for your domain. If your nameservers are wrong, nothing works — not your website, not your email, not your SSL verification.

Authoritative vs. Recursive Nameservers

These two types of nameservers are often confused. A recursive resolver (like 1.1.1.1 or 8.8.8.8) is the server your computer calls first. It does the legwork of walking the DNS tree to find an answer. An authoritative nameserver is the server that gives the definitive answer for a specific domain. When you change your nameservers at your registrar, you are changing which authoritative nameservers are responsible for your domain.

Registrars like GoDaddy, Namecheap, and Google Domains each provide default nameservers. If you move your hosting to SiteGround, WP Engine, or Cloudflare, they will give you a new set of nameservers to use instead. Changing those nameservers at your registrar is what delegates authority to your new provider.

What Nameservers Look Like

Nameservers are always hostnames, never IP addresses. A typical nameserver pair looks like this:

Most providers give you at least two nameservers for redundancy. If ns1 goes down, DNS queries fall over to ns2. Some providers give you four. Cloudflare, for example, assigns unique nameserver pairs per account, such as:

You need the exact hostnames your new host or DNS provider gives you. Do not guess or abbreviate them. A single typo means your domain stops resolving entirely.

How to Find Your Current Nameservers

Before you change anything, know what you are working with. You can look up the current authoritative nameservers for any domain using the DNS Lookup tool on this site — just enter your domain and select the NS record type. You can also run a quick command from your own terminal:

On Windows, use:

The response will list the current authoritative nameservers. Write these down before making any changes so you can roll back if needed.

How to Change Nameservers at Major Registrars

The process is essentially the same everywhere: log in, find your domain, find the nameserver settings, replace the old values, and save. Below are the exact steps for the most common registrars.

GoDaddy

1. Log in at godaddy.com and click your account name, then My Products.
2. Find your domain and click DNS next to it.
3. Scroll to the Nameservers section and click Change.
4. Select Enter my own nameservers (advanced).
5. Delete the existing entries and type in your new nameservers one per line.
6. Click Save and confirm the warning dialog.

Namecheap

1. Log in at namecheap.com and go to Domain List in the left sidebar.
2. Click Manage next to the domain you want to update.
3. Under the Nameservers section, open the dropdown and choose Custom DNS.
4. Enter your new nameservers in the fields provided. Click the green checkmark to add additional fields.
5. Click the green checkmark to save.

Google Domains / Squarespace Domains

1. Log in at domains.squarespace.com (Google Domains migrated here) and select your domain.
2. Click DNS in the left navigation.
3. Scroll to Nameservers and click Switch to custom nameservers.
4. Remove the existing nameservers and add your new ones.
5. Click Save.

Cloudflare Registrar

1. Log in at dash.cloudflare.com and go to Domain Registration.
2. Select your domain and click Configuration.
3. Under Nameservers, if you registered the domain at Cloudflare and also use Cloudflare DNS, the nameservers are managed automatically. If you want to point to an external provider, contact Cloudflare support — Cloudflare-registered domains default to using Cloudflare's own nameservers.

Hover

1. Log in at hover.com and click Domains.
2. Select your domain name.
3. Click the DNS tab.
4. Scroll to Nameservers and click Edit.
5. Remove the existing entries and add your new nameservers.
6. Click Save Nameservers.

Porkbun

1. Log in at porkbun.com and click Domain Management.
2. Click the domain name to expand its settings.
3. Click NS under the domain actions.
4. Clear the existing nameservers and enter your new ones.
5. Click Update.

How Long Does a Nameserver Change Take to Propagate

This is where patience is required. When you update your nameservers, the change does not take effect instantly everywhere in the world. The TLD registry (like Verisign for .com) needs to update its delegation record, and then cached records across thousands of resolvers worldwide need to expire based on their TTL (Time to Live) values.

In practice, most users will see the new nameservers within 1 to 4 hours. Full global propagation can take up to 48 hours, though it is rare for it to take that long anymore. The old 48-hour rule is largely outdated for most registrars and TLDs, but it does still apply in edge cases.

What Happens to Your Existing DNS Records

This is the part that trips people up most often. When you change nameservers, you are handing authority to a completely different DNS zone. Your existing DNS records at your old provider do not transfer automatically.

For example, if you have been using GoDaddy's default nameservers and you switch to Cloudflare, Cloudflare will attempt to import your existing records via a zone scan. That scan works reasonably well for common records but is not perfect. You must manually verify that all your A records, CNAME records, MX records, TXT records (including SPF and DKIM), and any SRV records exist and are correct at the new nameserver provider before you make the switch.

A common disaster scenario: someone switches nameservers to a new hosting provider, the website loads fine, but email stops working two days later because nobody recreated the MX records at the new DNS provider. Always audit your DNS zone before and after a nameserver change.

Pre-Change DNS Checklist

• Export or screenshot all DNS records from your current provider.
• Recreate every record at the new nameserver provider before switching.
• Verify MX records and SPF/DKIM TXT records specifically — email is the most common casualty.
• Lower your TTL values to 300 seconds (5 minutes) at your old provider a few hours before switching. This makes rollback faster if something goes wrong.
• Test the new DNS zone using your new provider's tools before flipping the switch.

How to Verify the Change Worked

Once you have made the update at your registrar, verify it from the command line. The key is to query the TLD nameservers directly rather than relying on your local resolver's cache:

This asks one of the .com TLD nameservers directly what it has on record for your domain's nameservers. If the output shows your new nameservers, the registrar-to-registry update went through successfully. If it still shows the old nameservers, the registrar may not have propagated the change to the registry yet — give it another hour and check again.

You can also verify the full DNS resolution chain:

This shows every step of the resolution process, from the root servers down to your authoritative nameservers. It is the most thorough way to confirm the entire delegation chain is intact.

Common Mistakes and How to Avoid Them

Typos in Nameserver Hostnames

Nameserver hostnames must be exact. A single extra character or wrong letter means the domain becomes completely unresolvable. Always copy-paste from your hosting provider's documentation or control panel rather than typing manually.

Removing Nameservers Without Adding New Ones

Some registrar interfaces let you delete nameservers without immediately saving new ones. If you accidentally save with no nameservers configured, your domain stops resolving immediately. Always have at least two valid nameservers entered before saving.

Forgetting Private/Glue Records

If your nameservers share the same domain as the domain you are managing (for example, ns1.example.com for the domain example.com), you need glue records. These are IP address records registered directly at the registry to break the circular dependency. This situation is uncommon for most users but critical for anyone running their own nameserver infrastructure.

Confusing DNS Hosting with Domain Registration

Your registrar is where you bought and manage your domain name. Your DNS hosting provider is where your DNS zone (all your records) lives. These can be the same company or different ones. When you change nameservers, you are changing your DNS hosting provider, not transferring your domain registration. Many people think they are moving their domain when they change nameservers — they are not.

When to Change Nameservers

Typical reasons to change nameservers include migrating to a new web host, enabling Cloudflare's proxy and security features, consolidating DNS management under one provider, or recovering from a compromised DNS account. Whatever the reason, the process is the same and takes only a few minutes of actual work. The waiting period for propagation is the longest part.

Armed with this understanding, a nameserver change should be a routine, low-stress task. The key is preparation: document your existing records, rebuild them at the new provider, then make the switch with confidence.