DNS & Domain Guides

Nameserver Basics: How to Delegate Your Zone

Learn what nameservers are, how DNS delegation works, when to change nameservers, and how to avoid common DNS zone mistakes.

By CheckDomainHealth Editorial Team Reviewed by Dionis Ceban Updated Jun 28, 2026 8 min read Beginner

Introduction

Nameservers decide which DNS provider controls the live DNS records for a domain. When a domain uses specific nameservers, the DNS zone at that provider becomes the authoritative source for records such as A, MX, TXT, CNAME and CAA.

Many DNS problems happen because users edit records in the wrong place. For example, a domain may be registered at one provider, hosted at another provider, and using Cloudflare or another DNS service for nameservers. In that case, only the active nameserver provider controls the live DNS zone.

Quick answer

Quick answer

Nameservers tell the internet which DNS provider is authoritative for a domain. Delegating a domain means setting its nameservers at the registrar so DNS queries are answered by the correct DNS zone. If nameservers point to one provider, DNS records edited somewhere else may not affect the live domain.

What are nameservers?

Nameservers are DNS servers that hold or reference the authoritative DNS zone for a domain. They answer DNS queries for records such as A, AAAA, MX, TXT, CNAME, NS and CAA.

Example 
example.com nameservers:
ns1.provider.com
ns2.provider.com

If these nameservers are active at the registrar, DNS records must usually be managed at that provider.

Registrar, nameserver and DNS zone

These three terms are often confused:

Registrar

The company where the domain is registered and renewed. Example: the place where you manage ownership, expiry and nameserver settings.

Nameservers

The DNS servers delegated at the registrar. They decide which DNS provider answers live DNS queries.

DNS zone

The set of DNS records for the domain, such as A, MX, TXT, CNAME and CAA.

A domain can be registered at Provider A, hosted at Provider B, and use DNS at Provider C. In that setup, DNS records must be edited at Provider C if Provider C’s nameservers are active.

How DNS delegation works

DNS delegation connects a domain at the registrar to the DNS provider that should answer queries for that domain.

  1. The domain owner sets nameservers at the registrar.
  2. The registry publishes those nameserver references.
  3. DNS resolvers ask the delegated nameservers for records.
  4. The authoritative DNS zone returns records such as A, MX or TXT.
  5. Browsers, mail servers and services use those records.

Changing nameservers is different from changing an A record or MX record. A nameserver change can move control of the entire DNS zone to another provider.

When to change nameservers

Moving DNS to another provider

Change nameservers when you want another DNS provider to control the domain’s records.

Using Cloudflare or another DNS/CDN platform

Many CDN/security platforms require changing nameservers so they can manage DNS and proxy traffic.

Moving from registrar DNS to hosting DNS

Some users delegate DNS to their hosting provider so DNS and hosting are managed in the same panel.

Consolidating DNS management

Agencies or businesses may move domains to one DNS provider for easier management.

Using advanced DNS features

Some providers offer better APIs, DNSSEC, monitoring, redundancy or traffic routing.

Do not change nameservers unless the new DNS zone already contains the required records for website, email, SSL and verification.

Before changing nameservers

Before changing nameservers, copy or recreate important DNS records at the new DNS provider.

  • A and AAAA records for website hosting
  • CNAME records for www, CDN or SaaS platforms
  • MX records for email routing
  • SPF, DKIM and DMARC TXT records
  • domain verification TXT/CNAME records
  • CAA records for SSL issuance
  • subdomains such as app, mail, panel, shop or client portals
  • any custom records used by third-party services

If these records are missing in the new zone, changing nameservers can break websites, email, SSL validation or service verification.

Why this matters

Why this matters

Nameservers matter because they decide which DNS zone is live. If the domain points to the wrong nameservers, your website, email, SSL validation and domain verification can fail even if the records look correct in another DNS panel. The most common mistake is editing DNS records at a provider that is not authoritative for the domain.

How to check nameservers

Use DNS Lookup or WHOIS Lookup to check which nameservers are currently active for the domain.

What to compare

When checking nameservers, compare these five values.

Current nameservers

The nameservers returned publicly for the domain.

Expected nameservers

The nameservers from your intended DNS provider.

DNS zone location

The provider where records are currently being edited.

Important records

A, MX, TXT, CNAME and CAA records that must exist in the active DNS zone.

Propagation state

Whether resolvers are still showing old nameservers after a recent change.

If DNS changes are not working, first confirm whether you are editing records at the active nameserver provider.

Check nameservers now

Use DNS Lookup to see which nameservers currently control your domain.

Run DNS Lookup →

Common nameserver problems

DNS edited at the wrong provider

High

The domain uses nameservers from one provider, but records are being changed in another DNS panel.

Next step: Check active nameservers and edit records only in the authoritative DNS zone.

New nameservers missing required records

High

After changing nameservers, the new DNS zone does not contain all website, email or verification records.

Next step: Recreate A, MX, TXT, CNAME, CAA and important subdomain records in the new zone.

Website works but email breaks after nameserver change

High

Website records were copied, but MX, SPF, DKIM or DMARC records were forgotten.

Next step: Compare the old and new DNS zones and restore missing mail records.

Nameserver change not visible everywhere yet

Low

Some resolvers may still show old nameservers due to caching.

Next step: Allow propagation time and check from multiple resolvers.

Domain still uses registrar default nameservers

Medium

The domain may not be delegated to the intended DNS or hosting provider.

Next step: Update nameservers at the registrar if another provider should control DNS.

Mixed or incomplete nameserver set

High

Only some nameservers were updated, or old and new nameservers are mixed.

Next step: Use the exact full nameserver set provided by the DNS provider.

Glue record problem for custom nameservers

Medium

Custom nameservers such as ns1.example.com may require glue records at the registrar.

Next step: Confirm glue records and IP addresses with the registrar or DNS provider.

DNSSEC mismatch after nameserver change

High

Old DNSSEC DS records may remain at the registrar after moving DNS providers.

Next step: Update or remove DS records according to the new DNS provider’s DNSSEC setup.

How to delegate or fix nameservers

  1. Identify the intended DNS provider

    Decide which provider should control DNS for the domain, such as registrar DNS, hosting DNS, Cloudflare or another DNS platform.

  2. Export or copy the current DNS records

    Before changing nameservers, save all existing DNS records, especially A, MX, TXT, CNAME, CAA and important subdomains.

  3. Create the DNS zone at the new provider

    Add the required records to the new DNS zone before changing nameservers. This reduces the risk of website or email downtime.

  4. Update nameservers at the registrar

    Log in to the registrar and replace the old nameservers with the exact nameservers provided by the new DNS provider.

    ns1.newprovider.com
ns2.newprovider.com
  5. Check propagation

    After saving the nameserver change, check whether public resolvers return the new nameservers. Some resolvers may still show the old ones until cache expires.

  6. Verify website and email records

    After delegation changes, check A/AAAA, CNAME, MX, SPF, DKIM, DMARC and CAA records in the live DNS zone.

  7. Monitor for issues

    Send test emails, load the website, check SSL and verify third-party services after the change.

Nameserver check examples

Nameserver lookup 
dig example.com NS
dig +short example.com NS
dig @8.8.8.8 example.com NS
dig @1.1.1.1 example.com NS
Delegation trace 
dig +trace example.com NS

These examples are for checking nameserver delegation only. Replace example.com with your actual domain.

Nameservers and email

Changing nameservers can affect email if the new DNS zone does not contain the correct mail records.

Before changing nameservers, make sure the new zone includes MX records, SPF TXT record, DKIM TXT records, DMARC TXT record, mail-related A/AAAA records if used, and verification records for Google Workspace, Microsoft 365 or other providers.

A website can continue working while email breaks, or email can continue working while the website breaks, depending on which records were copied correctly.

Nameservers, SSL and verification

SSL providers and SaaS platforms often use DNS records to verify domain ownership. If nameservers change and verification TXT or CNAME records are not copied, SSL issuance or service verification may fail.

  • CAA records
  • DNS validation TXT records
  • CDN verification records
  • Google/Microsoft/SaaS verification records
  • www and root domain records

Custom nameservers and glue records

Custom nameservers use hostnames under your own domain, such as ns1.example.com and ns2.example.com. Because these nameservers belong to the same domain they serve, the registrar may need glue records that map the nameserver hostnames to IP addresses.

Glue example 
ns1.example.com → 192.0.2.10
ns2.example.com → 192.0.2.11

Without correct glue records, resolvers may not be able to find the authoritative nameservers.

Custom nameservers are usually more advanced. Use provider nameservers unless you specifically need branded or self-managed nameservers.

Nameservers and DNSSEC

If DNSSEC is enabled, changing nameservers may also require updating DS records at the registrar. A DNSSEC mismatch can make the domain fail DNS validation for some resolvers.

Before moving DNS providers, check whether DNSSEC is enabled. If the new provider does not use the same DNSSEC keys, update or remove old DS records according to the new provider’s instructions.

Frequently asked questions

Are nameservers the same as DNS records?

No. Nameservers decide which DNS provider controls the domain. DNS records such as A, MX, TXT and CNAME live inside the DNS zone controlled by those nameservers.

Where do I change nameservers?

Nameservers are changed at the domain registrar, not usually inside the hosting control panel.

How long does a nameserver change take?

Some resolvers may show the new nameservers quickly, while others may continue using cached data for several hours.

Will changing nameservers break my website?

It can if the new DNS zone does not contain the correct website records. Always copy important records before changing nameservers.

Will changing nameservers break email?

It can if MX, SPF, DKIM or DMARC records are missing from the new DNS zone.

Can I use nameservers from two providers?

Usually you should use the complete nameserver set from one DNS provider. Mixing providers can cause inconsistent DNS answers unless you know exactly what you are doing.

What are glue records?

Glue records are registrar-level records that help resolve custom nameservers such as ns1.example.com when the nameserver hostname belongs to the same domain.

Do I need DNSSEC when changing nameservers?

Not always, but if DNSSEC is enabled, you must make sure DS records match the new DNS provider’s DNSSEC setup.

Use these free tools to verify your configuration after applying changes.

DNS Lookup WHOIS Lookup Domain Health Checker MX Lookup SPF Checker SSL Checker
Understanding DNS: How Domain Names Connect to Websites and Email 8 min read How to Run a Complete Domain Health Check 9 min read What Is an A Record and How to Configure It 7 min read MX Records 101: Directing Email to the Right Server 8 min read TXT Records: SPF, DKIM, DMARC and Beyond 8 min read Understanding TTL: DNS Cache and Propagation Times 8 min read
Browse all DNS & Domain guides →

Need help applying this fix?

Send us your domain, report link or issue details. CheckDomainHealth will review the request and route it to the right technical team if hands-on support is needed.

Get Help Run Domain Health Check

Was this guide helpful?

Your feedback helps us improve our guides for everyone.