How to Change Domain Nameservers: Complete Step-by-Step Guide (2025)

Quick Answer

Table of Contents

What Are Nameservers and Why Change Them?

What Are Nameservers?

Nameservers are specialized DNS servers that store and provide DNS records for your domain. They're the authoritative source for information about where your website is hosted, where email should be delivered, and other domain services.

Simple analogy: If your domain is a phone number, nameservers are the phone directory that tells callers where to reach you.

Nameserver Format

Nameservers typically look like:

ns1.cloudflare.com
ns2.cloudflare.com

Or:

dns1.registrar-servers.com
dns2.registrar-servers.com

Key characteristics:

• Usually come in pairs (minimum 2, often 2-4)
• Named systematically (ns1, ns2, ns3, etc.)
• Fully qualified domain names (FQDNs)
• Operated by DNS providers, registrars, or hosting companies

What Nameservers Control

When you change nameservers, you're changing where DNS records are managed:

DNS records controlled by nameservers:

• A records: Point domain to website IP address
• AAAA records: IPv6 website addresses
• MX records: Email server routing
• CNAME records: Subdomain aliases
• TXT records: Domain verification, SPF, DKIM
• CAA records: SSL certificate authorization
• SRV records: Service-specific routing

Example DNS zone managed by nameservers:

example.com.        A       93.184.216.34
www.example.com.    CNAME   example.com.
example.com.        MX 10   mail.example.com.
example.com.        TXT     "v=spf1 include:_spf.google.com ~all"

Why Change Nameservers?

Common reasons:

1. Switching Web Hosting Providers

• Moving from Bluehost to SiteGround
• Migrating to cloud hosting (AWS, Google Cloud)
• Changing to managed WordPress hosting

2. Using Dedicated DNS Services

• Cloudflare (performance, security, CDN)
• AWS Route53 (advanced features, API)
• Google Cloud DNS (Google infrastructure)
• NS1 (enterprise DNS management)

3. Better DNS Performance

• Faster DNS resolution (10-30ms vs 100-300ms)
• Global anycast networks
• Lower latency worldwide
• Better uptime (99.99%+)

4. Advanced Features

• DDoS protection (Cloudflare)
• Geo-routing (serve different content by location)
• Failover capabilities
• Real-time analytics
• API for automation

5. Consolidating Services

• Managing all domains at one DNS provider
• Unified control panel
• Bulk DNS updates
• Consistent interface

6. Security Improvements

• DNSSEC support
• DDoS mitigation
• CAA record management
• Access controls and audit logs

What Nameserver Changes DON'T Affect

Unchanged by nameserver changes:

• ❌ Domain registration (still at same registrar)
• ❌ Domain renewal dates
• ❌ Domain ownership
• ❌ WHOIS information
• ❌ Website hosting location (unless also migrating hosting)

Important: Changing nameservers only changes where DNS is managed, not domain registration.

Before You Change Nameservers

Critical Pre-Change Checklist

✅ Document Current DNS Records

Before changing nameservers, export or screenshot ALL current DNS records:

Why: Once nameservers change, you can't access old DNS records unless you documented them first.

How to export DNS records:

Option 1: Registrar/DNS Provider Interface

• Log into current DNS provider
• Navigate to DNS management
• Look for "Export Zone File" or "Export DNS"
• Download as text file

Option 2: Command Line (dig)

# Export all DNS records
dig example.com ANY +noall +answer > dns-backup.txt

# Check specific record types
dig example.com A
dig example.com MX
dig example.com TXT

Option 3: Online Tools

• MXToolbox DNS Lookup
• DNS Checker
• Screenshot results for all record types

Records to document:

A records:        @ and www
AAAA records:     IPv6 addresses
MX records:       Email routing
TXT records:      SPF, DKIM, DMARC, verification
CNAME records:    [Subdomains](/kb/getting-started/what-is-a-subdomain)
SRV records:      Services
CAA records:      SSL certificate authorities

✅ Get New Nameserver Information

Obtain nameserver addresses from new provider:

From web hosting provider:

• Check welcome email (usually contains nameservers)
• Log into hosting control panel
• Look for "Nameservers" or "DNS Information"

From DNS service (Cloudflare, Route53, etc.):

• Add domain to DNS service
• Provider assigns nameservers
• Usually shown during setup process

Example nameserver information:

Primary Nameserver:   ns1.newprovider.com
Secondary Nameserver: ns2.newprovider.com
Optional Third:       ns3.newprovider.com
Optional Fourth:      ns4.newprovider.com

✅ Recreate DNS Records at New Provider

Before changing nameservers, recreate all DNS records at new provider:

Process:

1. Log into new DNS provider
2. Navigate to DNS record management
3. Add all A, AAAA, MX, TXT, CNAME records
4. Match exactly to documented records
5. Verify records are correct
6. Don't change nameservers yet

Why this order: Ensures DNS records exist at new provider before switching nameservers, preventing downtime.

✅ Lower TTL Values (Optional but Recommended)

TTL (Time to Live) determines how long DNS records are cached.

Current TTL (typical): 3600 seconds (1 hour) to 86400 seconds (24 hours)

Recommended pre-change:

• 24-48 hours before nameserver change
• Lower TTL to 300-600 seconds (5-10 minutes)
• Allows faster DNS updates during transition

How to change TTL:

1. Log into current DNS provider
2. Edit each DNS record
3. Change TTL field to 300 or 600
4. Save changes
5. Wait current TTL period before changing nameservers

After nameserver change: Change TTL back to 3600-86400 (reduces DNS query load)

✅ Choose Low-Traffic Time

Schedule nameserver changes during:

• Nights/weekends (for business sites)
• Off-peak hours (check Google Analytics)
• When technical support is available
• When you can monitor the change

Avoid:

• Black Friday, Cyber Monday (e-commerce)
• Product launches
• Major campaigns
• Peak business hours

✅ Notify Stakeholders

Inform relevant people:

• Development team
• IT department
• Email administrators
• Business stakeholders

What to communicate:

• Scheduled change time
• Expected duration (24-48 hours)
• Potential brief email/website disruptions
• Contact person for issues

Getting Your New Nameserver Information

From Web Hosting Providers

Different hosting providers display nameservers in different locations:

cPanel Hosting (SiteGround, A2 Hosting, etc.):

1. Log into cPanel
2. Scroll to "General Information" section
3. Look for "Name Server" or "DNS"
4. Copy nameserver addresses

Kinsta (Managed WordPress):

• Welcome email contains nameservers
• Or: Dashboard → DNS → Nameservers
• Format: ns1.kinsta.cloud, ns2.kinsta.cloud

WP Engine:

• Dashboard → Sites → Your Site → "DNS"
• Format: ns1.wpengine.com, ns2.wpengine.com

Bluehost:

• Log in → Domains → Manage
• Click domain → Nameserver settings
• Format: ns1.bluehost.com, ns2.bluehost.com

HostGator:

• cPanel → General Information
• Format: ns1.hostgator.com, ns2.hostgator.com

From Dedicated DNS Providers

Cloudflare:

1. Add domain to Cloudflare account
2. Cloudflare scans existing DNS records
3. Assigned nameservers displayed on screen
4. Format: charlie.ns.cloudflare.com, dana.ns.cloudflare.com
5. Important: Each domain gets unique nameservers

AWS Route53:

1. Create hosted zone for domain
2. AWS assigns 4 nameservers
3. Format: ns-123.awsdns-12.com, ns-456.awsdns-45.net, etc.
4. Each hosted zone has unique nameservers

Google Cloud DNS:

1. Create DNS zone
2. Google assigns nameservers
3. Format: ns-cloud-a1.googledomains.com, ns-cloud-a2.googledomains.com, etc.

NS1:

1. Add domain to NS1
2. Nameservers assigned
3. Format: dns1.p01.nsone.net, dns2.p01.nsone.net, etc.

Nameserver Requirements

Minimum requirements:

• At least 2 nameservers (ICANN requirement)
• Maximum 13 nameservers (practical limit)
• Different IP addresses (redundancy)

Best practices:

• Use 2-4 nameservers
• Nameservers on different networks (automatic with most providers)
• All from same provider (consistency)

Example valid nameserver sets:

2 nameservers (minimum):

ns1.provider.com
ns2.provider.com

4 nameservers (recommended):

ns1.provider.com
ns2.provider.com
ns3.provider.com
ns4.provider.com

Validating Nameserver Addresses

Before using nameservers, verify they're valid:

Test nameserver resolution:

# Check if nameserver resolves
nslookup ns1.cloudflare.com

# Should return IP addresses
Non-authoritative answer:
Name:    ns1.cloudflare.com
Address: 173.245.58.185
Address: 2606:4700:58::adf5:3ab9

If nameserver doesn't resolve: Double-check spelling or contact provider

How to Change Nameservers: Universal Steps

These steps apply to virtually all domain registrars:

Step 1: Log Into Your Domain Registrar

Not your hosting provider—your registrar (where you purchased the domain):

• GoDaddy, Namecheap, Cloudflare Registrar, Porkbun, etc.

How to find your registrar:

whois example.com | grep "Registrar:"

Step 2: Navigate to Domain Management

Common navigation paths:

• Domains → My Domains → Manage
• Domain List → Click domain name
• Dashboard → Domains → Settings
• My Account → Domains → Manage DNS

Step 3: Find Nameserver Settings

Look for:

• "Nameservers"
• "DNS Management" or "DNS Settings"
• "Name Servers"
• "Custom DNS"

Common locations:

• Dedicated "Nameservers" tab
• Under "DNS" or "Advanced DNS"
• Domain settings page
• "Change Nameservers" button

Step 4: Select Custom/External Nameservers

Most registrars default to their own nameservers. You need to switch to custom:

Options you might see:

• "Use custom nameservers" (select this)
• "Use external nameservers"
• "Third-party nameservers"
• vs. "Use [Registrar] nameservers"

Step 5: Enter New Nameserver Addresses

Input fields:

• Nameserver 1: ns1.newprovider.com
• Nameserver 2: ns2.newprovider.com
• Nameserver 3: ns3.newprovider.com (optional)
• Nameserver 4: ns4.newprovider.com (optional)

Important details:

• ✅ Enter exactly as provided (case-insensitive but be accurate)
• ✅ Include full domain name (e.g., ns1.cloudflare.com, not just ns1)
• ✅ No "http://" or "https://" prefix
• ✅ No trailing periods (some systems add automatically)

Common mistakes:

• ❌ Entering IP addresses instead of nameserver names
• ❌ Typos in nameserver addresses
• ❌ Mixing nameservers from different providers
• ❌ Using only 1 nameserver (minimum 2 required)

Step 6: Save Changes

• Click "Save," "Update," or "Change Nameservers"
• Confirm changes if prompted
• Some registrars send confirmation email

Confirmation messages:

• "Nameservers successfully updated"
• "Changes may take up to 48 hours to propagate"
• "DNS settings updated"

Step 7: Wait for DNS Propagation

Timeline: 15 minutes to 48 hours (typically 4-24 hours)

What's happening:

• Registry updates TLD zone file (1-4 hours)
• ISPs and DNS resolvers cache old nameservers
• Gradually, cached data expires and updates
• Users worldwide see new nameservers at different times

During this time:

• Some visitors see old site/email
• Some see new site/email
• This is normal and temporary

Registrar-Specific Instructions

Namecheap

Steps:

1. Log in to namecheap.com
2. Click "Domain List" in left sidebar
3. Click "Manage" next to your domain
4. Scroll to "Nameservers" section
5. Select "Custom DNS" from dropdown
6. Enter nameserver addresses (2-4)
7. Click green checkmark to save

Nameserver fields: Labeled "Nameserver 1," "Nameserver 2," etc.

Propagation: Typically 30 minutes to 48 hours

GoDaddy

Steps:

1. Log in to godaddy.com
2. Go to "My Products" → "Domains"
3. Click three dots (⋮) next to domain → "Manage DNS"
4. Scroll down to "Nameservers" section
5. Click "Change" button
6. Select "I'll use my own nameservers"
7. Enter nameserver addresses
8. Click "Save"

Note: GoDaddy may show warning about losing DNS settings—this is expected.

Cloudflare Registrar

Steps:

1. Log in to dash.cloudflare.com
2. Select domain
3. Go to "DNS" → "Records"
4. Scroll to "Cloudflare Nameservers"
5. Already set to Cloudflare nameservers (automatic)

Note: Domains registered at Cloudflare must use Cloudflare nameservers (can't change to external).

Porkbun

Steps:

1. Log in to porkbun.com
2. Click domain name
3. Click "Authoritative Nameservers" section
4. Enter new nameservers (minimum 2)
5. Click "Update Nameservers"

Interface: Clean, straightforward nameserver management

Google Domains → Squarespace

Steps (after Google Domains migration to Squarespace):

1. Log in to domains.squarespace.com
2. Click domain name
3. Click "DNS Settings"
4. Scroll to "Name Servers"
5. Click "Use Custom Name Servers"
6. Enter nameserver addresses
7. Save changes

Dynadot

Steps:

1. Log in to dynadot.com
2. Go to "My Domains"
3. Click domain name
4. Click "DNS Settings"
5. Select "Name Servers"
6. Choose "Use These Name Servers"
7. Enter nameserver addresses
8. Save

NameSilo

Steps:

1. Log in to namesilo.com
2. Account Domains → Domain Manager
3. Click blue icon next to domain
4. Select "Change Nameservers"
5. Enter new nameservers
6. Submit changes

Network Solutions

Steps:

1. Log in to networksolutions.com
2. Go to "Account Manager"
3. Click "My Domain Names"
4. Select domain → "Manage"
5. Click "Change Where Domain Points"
6. Select "Domain Name Server (DNS)"
7. Enter nameservers
8. Click "Apply Changes"

Hover

Steps:

1. Log in to hover.com
2. Click domain name
3. Click "Nameservers" tab
4. Select "Custom"
5. Enter nameserver addresses
6. Click "Save Nameservers"

DNS Propagation: What to Expect

What Is DNS Propagation?

DNS propagation is the time it takes for nameserver changes to update across the global DNS system.

Why it takes time:

• DNS is cached at multiple levels (browsers, ISPs, DNS resolvers)
• Each cache has a TTL (Time to Live) that must expire
• Thousands of DNS servers worldwide must update
• Updates don't happen simultaneously

Propagation Timeline

0-15 minutes: Registry zone file updates

• TLD nameservers (.com, .net, etc.) receive updates
• New nameservers now authoritative at registry level

15 minutes - 4 hours: Early propagation

• Some DNS resolvers update
• Close geographic locations may see changes
• New DNS queries get new nameservers

4-24 hours: Majority propagation

• Most users worldwide see new nameservers
• Old TTLs expiring
• Cached data being replaced

24-48 hours: Full propagation

• 99%+ of global DNS updated
• Stragglers with long cache times updating
• Considered fully propagated

Factors affecting speed:

• Previous TTL values (lower = faster)
• DNS resolver behavior (some cache longer than TTL)
• Geographic distribution
• ISP DNS server refresh rates

What Users Experience During Propagation

Scenario 1: Website Visitor

• User in New York might see new site (updated DNS)
• User in London might see old site (cached DNS)
• Same user refreshing might see different sites as local cache updates

Scenario 2: Email

• Some emails deliver to old server (old MX records)
• Some deliver to new server (new MX records)
• Both servers should be accepting email during transition (if possible)

Scenario 3: Subdomains

• www.example.com might update before blog.example.com
• Different DNS record types update independently
• All eventually converge to new nameservers

Monitoring Propagation

Online tools:

WhatsmyDNS.net:

• Check nameservers from 30+ locations worldwide
• Select "NS" record type
• Enter your domain
• Green checkmarks = updated to new nameservers

DNS Checker:

• Similar to WhatsmyDNS
• Shows propagation status globally

Command-line monitoring:

Check current nameservers:

dig NS example.com +short

Check against specific DNS server:

# Google DNS
dig NS example.com @8.8.8.8 +short

# Cloudflare DNS
dig NS example.com @1.1.1.1 +short

# Your ISP DNS
dig NS example.com +short

If results differ: Propagation still in progress

Track propagation percentage:

# Check multiple DNS servers
for server in 8.8.8.8 1.1.1.1 9.9.9.9 208.67.222.222; do
  echo "DNS Server: $server"
  dig NS example.com @$server +short
  echo
done

Verifying Nameserver Changes

Immediate Verification (Registry Level)

Check registry immediately after changing nameservers:

whois example.com | grep "Name Server"

Expected output:

Name Server: NS1.NEWPROVIDER.COM
Name Server: NS2.NEWPROVIDER.COM

Timeframe: Updates within 15 minutes to 2 hours at registry

DNS Query Verification

Check authoritative nameservers:

dig NS example.com +short

Should return:

ns1.newprovider.com.
ns2.newprovider.com.

If showing old nameservers: DNS resolver is showing cached data (wait for propagation)

Website Verification

Test website loading:

1. Open browser in incognito/private mode (avoids browser cache)
2. Visit your domain
3. Verify correct website loads

If wrong site loads:

• Check from different network (mobile data vs WiFi)
• Use VPN to test from different geographic location
• Wait for propagation to complete

Check specific DNS records:

# Check A record (website IP)
dig A example.com +short

# Should match new DNS provider's A record

Email Verification

Test email sending/receiving:

1. Send test email to [email protected]
2. Send test email from [email protected]
3. Check email headers for MX routing

Check MX records:

dig MX example.com +short

Should return new MX records from new DNS provider

If email issues:

• Verify MX records configured at new DNS provider
• Check SPF, DKIM, DMARC records migrated
• Test from multiple email providers (Gmail, Outlook, etc.)

SSL Certificate Verification

Check SSL certificate:

1. Visit https://yourdomain.com
2. Click padlock icon → Certificate
3. Verify certificate is valid and matches domain

If SSL errors:

• Wait for DNS propagation
• Verify CAA records (if used) are correct
• Contact hosting provider if issues persist

Common Nameserver Change Scenarios

Scenario 1: Moving to Cloudflare

Why: Performance, security, CDN, DDoS protection

Steps:

1. Create Cloudflare account
2. Add domain to Cloudflare
3. Cloudflare scans existing DNS records
4. Review and verify all records imported correctly
5. Add any missing records
6. Cloudflare assigns unique nameservers (e.g., charlie.ns.cloudflare.com)
7. Change nameservers at registrar to Cloudflare's assigned nameservers
8. Wait for propagation
9. Cloudflare confirms when active

Expected outcome:

• DNS managed by Cloudflare
• Traffic routed through Cloudflare network
• DDoS protection active
• SSL/TLS encryption available

Timeline: 5-10 minutes setup, 24-48 hours full propagation

Scenario 2: New Web Hosting Provider

Why: Switching from Bluehost to SiteGround (example)

Steps:

1. Sign up for SiteGround hosting
2. Migrate website files to SiteGround
3. Get SiteGround nameservers (welcome email or cPanel)
4. Before changing nameservers: Recreate all DNS records at SiteGround
   • A records for domain and www
   • MX records for email
   • Any CNAME, TXT records
5. Test website using SiteGround's temporary URL
6. Change nameservers at registrar to SiteGround nameservers
7. Monitor DNS propagation
8. Verify website and email working

Expected outcome:

• Website served from SiteGround servers
• DNS managed by SiteGround
• Email routing unchanged (if MX records recreated correctly)

Timeline: 1-2 hours setup, 24-48 hours propagation

Scenario 3: Using AWS Route53

Why: Advanced DNS features, API control, enterprise requirements

Steps:

1. Create AWS account
2. Navigate to Route53
3. Create hosted zone for your domain
4. AWS assigns 4 nameservers
5. Add DNS records to hosted zone (A, MX, CNAME, TXT, etc.)
6. Verify records in Route53 console
7. Change nameservers at registrar to Route53's 4 nameservers
8. Wait for propagation

Expected outcome:

• DNS managed via AWS Route53
• Access to advanced routing policies (geolocation, failover, weighted)
• API access for automation
• Integration with other AWS services

Cost: ~$0.50/month per hosted zone + query charges (very low)

Scenario 4: Separating DNS from Hosting

Why: Flexibility, better performance, avoid coupling

Current state: Domain registered at GoDaddy, using GoDaddy nameservers and hosting

Goal: Keep GoDaddy registration, use Cloudflare DNS, use SiteGround hosting

Steps:

1. Set up hosting at SiteGround, note server IP
2. Add domain to Cloudflare
3. In Cloudflare DNS:
   • Add A record: @ → SiteGround IP
   • Add A record: www → SiteGround IP
   • Add MX records for email
   • Add all other necessary records
4. Change GoDaddy nameservers to Cloudflare nameservers
5. Wait for propagation

Result:

• Registration: GoDaddy (renew domain here)
• DNS: Cloudflare (manage DNS records here)
• Hosting: SiteGround (website files stored here)

Benefits: Best-of-breed services, flexibility to change hosting without DNS changes

Scenario 5: Reverting Nameserver Changes

Why: New provider having issues, need to rollback

Steps:

1. Get old nameserver addresses (check email records or WHOIS history)
2. Log into registrar
3. Change nameservers back to original addresses
4. Save changes
5. Wait for propagation (reverting takes same time as initial change)

If you don't have old nameserver addresses:

• Check email for old hosting provider information
• Contact old provider for nameserver details
• Use WHOIS history service to look up old nameservers

Preventing Downtime During Nameserver Changes

Zero-Downtime Nameserver Change Strategy

Goal: Change nameservers with no website or email interruption

Complete pre-change preparation:

Week Before Change:

1. ✅ Document all DNS records
2. ✅ Export DNS zone file
3. ✅ Reduce TTL to 300-600 seconds
4. ✅ Identify peak vs. low-traffic times

Day Before Change:

1. ✅ Recreate ALL DNS records at new provider
2. ✅ Verify records with dig before switching nameservers
3. ✅ Set up monitoring (UptimeRobot, Pingdom)
4. ✅ Notify team/stakeholders

During Change:

1. ✅ Schedule during low-traffic period
2. ✅ Change nameservers at registrar
3. ✅ Immediately verify nameserver change in WHOIS
4. ✅ Monitor website/email continuously

After Change:

1. ✅ Test website from multiple locations
2. ✅ Send/receive test emails
3. ✅ Check SSL certificate
4. ✅ Monitor analytics for traffic drops
5. ✅ After 48 hours: Increase TTL back to normal

Email Continuity Strategy

Problem: Email could be delivered to old or new server during propagation

Solution 1: Dual Email Servers (Best for critical email)

During transition:

• Keep email active on old server
• Set up email on new server
• Both servers accept incoming email
• After 72 hours, migrate from old to new

Process:

1. Set up email on new hosting/provider
2. Configure identical email accounts
3. Leave MX records pointing to old server in new DNS
4. Change nameservers (MX still pointing to old server)
5. After propagation complete (48 hours):
   • Update MX records to new server
   • Wait another 24-48 hours
6. Migrate email from old to new server
7. Deactivate old email server

Solution 2: External Email Provider (Recommended)

Use third-party email (Gmail, Outlook, etc.):

• Email never tied to hosting
• MX records point to Google/Microsoft servers
• Nameserver changes don't affect email

Benefits:

• No email downtime during any hosting/DNS changes
• Better email reliability
• Professional email features

Website Continuity Strategy

Ensure website stays live:

1. Migrate Website BEFORE Nameserver Change:

• Upload all files to new hosting
• Set up databases
• Test using temporary URL
• Verify everything works
• Then change nameservers

2. Use Same IP Addresses (if possible):

• If switching DNS providers but not hosting
• Use same A record values
• Seamless transition

3. Set Up Redirects (if changing domains):

• 301 redirects from old to new
• Preserve SEO
• Prevent broken links

4. CDN/Proxy (like Cloudflare):

• CDN caches content
• Serves cached content during DNS changes
• Minimizes impact on visitors

Monitoring During Transition

Set up monitoring before changing nameservers:

UptimeRobot (free):

• HTTP monitoring (checks if website up)
• Keyword monitoring (checks for specific content)
• SSL monitoring
• Alerts via email, SMS, Slack

Pingdom:

• Global monitoring from multiple locations
• Performance tracking
• Real user monitoring

StatusCake:

• Uptime monitoring
• Page speed monitoring
• Domain expiry monitoring

Configure alerts:

• Website down
• Response time >3 seconds
• SSL errors
• HTTP error codes (500, 503, etc.)

Troubleshooting Nameserver Issues

Problem 1: "Invalid Nameserver" Error

Error message: "Invalid nameserver address" or "Nameserver not found"

Causes:

• Typo in nameserver address
• Nameserver doesn't exist
• Nameserver not registered

Solutions:

1. Double-check spelling: ns1.cloudflare.com not ns1.cloudfare.com
2. Test nameserver resolution:

   nslookup ns1.cloudflare.com
   

   Should return IP addresses
3. Copy-paste nameservers (don't type manually)
4. Verify nameservers with DNS provider

Problem 2: Nameservers Changed but Website Still Shows Old Content

Cause: DNS propagation in progress OR browser/local caching

Solutions:

Clear local DNS cache:

Windows:

ipconfig /flushdns

macOS:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Linux:

sudo systemd-resolve --flush-caches

Test from different network:

• Use mobile data (different ISP)
• Use VPN to different location
• Ask friend in different location to test

Check DNS propagation:

• Visit whatsmydns.net
• Check if nameservers updated globally
• If still propagating, wait 24-48 hours

Verify A record:

dig A example.com +short

Compare to expected IP address at new host

Problem 3: Email Stopped Working After Nameserver Change

Cause: MX records not configured at new DNS provider

Solution:

Check current MX records:

dig MX example.com +short

If no results or wrong servers:

1. Log into new DNS provider
2. Add MX records:

   Priority: 10, Mail Server: mail.example.com
   

   Or for Google Workspace:

   Priority: 1,  Mail Server: aspmx.l.google.com.
   Priority: 5,  Mail Server: alt1.aspmx.l.google.com.
   Priority: 5,  Mail Server: alt2.aspmx.l.google.com.
   Priority: 10, Mail Server: alt3.aspmx.l.google.com.
   Priority: 10, Mail Server: alt4.aspmx.l.google.com.
   

3. Save MX records
4. Wait 1-2 hours for propagation
5. Test email send/receive

Also check:

• SPF record (TXT record for email authentication)
• DKIM record (email signing)
• DMARC record (email policy)

Problem 4: "Nameserver Change Not Allowed"

Error: Registrar won't let you change nameservers

Possible causes:

1. Domain Locked:

• Domain has transfer lock enabled
• Unlock domain first
• Then change nameservers

2. Recent Transfer (60-day lock):

• Domains locked for 60 days after transfer
• Wait until lock period ends
• Check WHOIS for transfer date

3. Registry Lock:

• High-value domains may have registry-level lock
• Contact registrar to remove
• May require additional verification

4. Expired Domain:

• Domain must be active to change nameservers
• Renew domain first

5. Billing Issues:

• Unpaid invoices at registrar
• Resolve payment issues
• Then retry nameserver change

Problem 5: Nameservers Keep Reverting

Cause: Registrar requires additional verification or has security lock

Solutions:

1. Check for 2FA requirement on changes
2. Verify email confirmation links
3. Contact registrar support
4. Check for security locks in account settings
5. Verify account ownership (may require ID verification)

Problem 6: Website Down After Nameserver Change

Immediate steps:

1. Check nameservers are correct:

dig NS example.com +short

2. Check A record points to correct IP:

dig A example.com +short

Compare to hosting provider's IP

3. Verify DNS records at new provider:

• Log into new DNS provider
• Ensure A record exists for @ and www
• Verify IP address is correct

4. Test direct IP access:

• Visit http://[IP-ADDRESS] in browser
• If site loads by IP but not domain: DNS issue
• If doesn't load by IP: hosting issue

5. Check with new DNS provider directly:

# Query new nameserver directly
dig @ns1.newprovider.com example.com +short

If returns correct IP: Propagation issue, wait If returns no result or wrong IP: DNS record misconfigured

Quick fix: Temporarily revert to old nameservers while debugging

Advanced: Custom Nameservers

What Are Custom Nameservers?

Custom nameservers (also called "vanity nameservers") use your own domain instead of your DNS provider's domain.

Standard nameservers:

ns1.cloudflare.com
ns2.cloudflare.com

Custom nameservers:

ns1.yourdomain.com
ns2.yourdomain.com

Why use custom nameservers:

• Professional branding (for agencies, hosting resellers)
• White-label DNS services
• Brand consistency
• Client perception (looks more established)

Setting Up Custom Nameservers

Requirements:

• Access to domain registrar
• IP addresses of actual nameservers

Process:

Step 1: Register Nameserver Hostnames

At your domain registrar:

1. Navigate to "Register Nameserver" or "Glue Records"
2. Create nameserver hostnames:
   • Hostname: ns1.yourdomain.com
   • IP Address: 173.245.58.1 (your DNS provider's IP)
   • Hostname: ns2.yourdomain.com
   • IP Address: 173.245.59.1 (your DNS provider's IP)
3. Save glue records

Step 2: Use Custom Nameservers

For client domains (or other domains):

1. Set nameservers to your custom nameservers:

   ns1.yourdomain.com
   ns2.yourdomain.com
   

2. DNS queries route to underlying DNS provider

Example Setup (Cloudflare custom nameservers):

1. Get Cloudflare nameserver IPs:

   dig ns1.cloudflare.com +short
   173.245.58.1
   

2. Register glue records at registrar:
   • ns1.yourdomain.com → 173.245.58.1
   • ns2.yourdomain.com → 173.245.59.1
3. Configure Cloudflare to accept queries for ns1.yourdomain.com
4. Point domains to ns1.yourdomain.com, ns2.yourdomain.com

Use cases:

• Web hosting companies offering DNS to customers
• Agencies managing client domains
• SaaS platforms with custom domains

Frequently Asked Questions

How long does it take for nameserver changes to take effect?

Nameserver changes typically take 24-48 hours to fully propagate globally, though you may see changes within 4-8 hours. The registry updates within 15 minutes to 2 hours, but ISPs and DNS resolvers cache old nameservers based on TTL values, causing gradual propagation.

Will changing nameservers affect my website?

Changing nameservers should not cause downtime if done correctly. The key is to recreate all DNS records (A, MX, CNAME, TXT) at the new DNS provider before changing nameservers. If records are missing at the new provider, your website or email may experience issues during propagation.

Can I change nameservers without changing hosting?

Yes, absolutely. Changing nameservers only changes where DNS is managed, not where your website is hosted. For example, you can switch to Cloudflare nameservers for DNS management while keeping your website at SiteGround hosting—just ensure the A record points to SiteGround's IP address.

How many nameservers do I need?

You need a minimum of 2 nameservers (ICANN requirement), but 3-4 nameservers are recommended for redundancy. Most DNS providers give you 2-4 nameservers automatically. Using nameservers from the same provider ensures consistency.

What happens if I enter the wrong nameservers?

If you enter incorrect nameservers, your domain will stop resolving (website and email won't work) once propagation completes. To fix: log into your registrar, correct the nameserver addresses, and wait for propagation. Your website/email will return once correct nameservers propagate.

Do nameserver changes affect email?

Nameserver changes can affect email if MX records aren't configured at the new DNS provider. Before changing nameservers, ensure all email-related DNS records (MX, SPF, DKIM, DMARC) are recreated at the new provider to prevent email disruption.

Can I use nameservers from different providers?

Not recommended. All nameservers for a domain should be from the same provider. Mixing nameservers from different providers (e.g., ns1.cloudflare.com and ns1.route53.com) causes inconsistent DNS responses and creates conflicts. Always use a complete set from one provider.

How do I check if my nameserver change is complete?

Check propagation using online tools like whatsmydns.net or command-line:

dig NS example.com +short

If results show your new nameservers globally (green checkmarks on whatsmydns.net), propagation is complete. This typically takes 24-48 hours.

What is the difference between nameservers and DNS records?

Nameservers determine where DNS records are stored and managed (e.g., Cloudflare, Route53). DNS records are the actual data (A, MX, CNAME) that specify where your website and email are hosted. Changing nameservers changes who manages your DNS records.

Can I change nameservers back if something goes wrong?

Yes, you can revert to old nameservers anytime by logging into your registrar and entering the previous nameserver addresses. Reverting takes the same propagation time (24-48 hours) as the initial change. Always save your old nameserver addresses before changing.

Key Takeaways

✅ Nameservers determine where DNS records are managed—changing them doesn't move your website, just DNS control

✅ Recreate all DNS records at new provider BEFORE changing nameservers to prevent downtime

✅ Minimum 2 nameservers required (ICANN policy); most providers give 2-4 for redundancy

✅ DNS propagation takes 24-48 hours—changes aren't instant due to global DNS caching

✅ Lower TTL values 24-48 hours before changing (to 300-600 seconds) for faster propagation

✅ Email requires MX, SPF, DKIM, and DMARC records—must be recreated at new DNS provider to avoid email disruption

✅ Test nameserver changes using dig, nslookup, or whatsmydns.net to verify propagation status

✅ Registrar vs DNS provider: Registrar is where domain is registered; nameservers point to DNS provider (can be same or different)

✅ Schedule changes during low-traffic times and monitor website/email during 48-hour propagation window

✅ You can revert nameserver changes if issues occur—keep old nameserver addresses saved