DNS errors when migrating a GoDaddy domain almost always trace back to one of three things: changing nameservers too early, a high TTL slowing propagation, or DNS records that weren't copied to the new provider. Follow the right sequence and you avoid hours — or days — of downtime.
This guide covers the most common errors that happen during and after migrating a domain from GoDaddy, with concrete steps to fix each one.
Why DNS Migration Is Tricky
When you migrate a domain from GoDaddy, you're changing who controls the nameservers that tell the world where your site lives. That change isn't instant: DNS uses caching (TTL) to reduce load, and while servers around the world update their caches, your domain can respond inconsistently.
The two most common migration scenarios:
- Full domain transfer (changing registrar): you move ownership from GoDaddy to another registrar like Namecheap, Hostinger, or your new hosting provider.
- Nameserver change only: the domain stays at GoDaddy but you point to your new host's nameservers. Faster, no 5-7 day transfer window.
The Most Common DNS Errors When Migrating From GoDaddy
Site Won't Load After Changing Nameservers
This is the most-reported issue. Common causes:
- The old nameservers had a high TTL (24-48 hours) and ISPs still have stale cache.
- The new nameservers don't yet have all DNS records (A, MX, CNAME, TXT) configured.
Fix:
- Before touching nameservers, reduce the TTL on all your DNS records in GoDaddy to 600 seconds (10 minutes). Wait the equivalent of the old TTL for caches to expire.
- At the new host, configure all DNS records (A, www, MX, SPF, DKIM, etc.) before switching nameservers.
- Switch the nameservers and wait. With a low TTL propagation can take 15-30 minutes; with a high TTL, up to 48 hours.
Email Stops Working
Email uses separate MX records. If you forget to copy them to the new provider, incoming mail goes to a server that no longer exists (or doesn't exist yet).
Fix: Before changing any nameservers, export or note every DNS record from GoDaddy's DNS Management panel: A, AAAA, CNAME, MX, TXT, and SRV. Paste them into your new host's DNS panel before making the switch.
Domain Is "Locked" During Transfer
GoDaddy locks domains against transfer by default. If you try to transfer without unlocking first, the request fails or stays pending indefinitely.
Step-by-step fix:
- In GoDaddy → My Domains → select the domain → Settings.
- Disable Domain Lock.
- Request the Authorization Code (EPP Code) — it arrives by email within minutes.
- Start the transfer at the new registrar using that code.
- Confirm the transfer from the GoDaddy confirmation email (you have 5 days; if you don't confirm, GoDaddy rejects it automatically).
ERR_NAME_NOT_RESOLVED
If the domain shows this error after changing nameservers, the new nameservers are likely misspelled or the DNS zone hasn't been created at the new host.
Quick diagnosis:
- Check current nameservers with:
nslookup -type=NS yourdomain.com 8.8.8.8 - Compare with what your new host provided. A single character difference will cause failure.
- Confirm in your new host's panel that the DNS zone is created and has at least one A record pointing to the correct IP.
Site Loads for Some Users but Not Others
This means propagation is still underway: some ISPs have updated their cache, others still have the old address. It's normal during the first 24-48 hours.
What you can do:
- Use dnschecker.org to track propagation status by region.
- Ask affected users to flush their local DNS cache:
ipconfig /flushdns(Windows) orsudo dscacheutil -flushcache(Mac). - For business-critical sites, keep both servers live for 48 hours during the cutover window.
Reference Table: Symptom → Cause → Fix
| Symptom | Likely Cause | Fix |
|---|---|---|
| Site won't load after switch | High TTL or missing records | Lower TTL first; copy all records before switch |
| Email not working | MX records not copied | Export MX from GoDaddy and add to new host |
| Transfer blocked | Domain Lock on or no EPP Code | Unlock domain and request EPP Code |
| ERR_NAME_NOT_RESOLVED | Misspelled nameservers or no zone | Verify with nslookup; create zone at new host |
| Inconsistent propagation | ISP DNS cache still updating | Wait 48 h; monitor with dnschecker.org |
Best Practices for a Clean DNS Migration
Preparation beats speed every time. Follow this sequence and you'll avoid 95% of problems:
- Export all DNS records from GoDaddy before touching anything.
- Lower the TTL to 600 seconds at least 24 hours in advance (if the current TTL is high).
- Configure all records at the new host and verify the site loads from the new IP before switching nameservers (edit your local hosts file to test this).
- Change the nameservers at GoDaddy only once the new host is fully ready.
- Monitor for 48 hours with dnschecker.org and an uptime tool.
- Raise the TTL back to 3600 or 86400 seconds once propagation is complete.
If the process feels complex or the domain is business-critical, having an experienced team handle it is worth every peso. The specialists at elenlace.com manage domain migrations with zero downtime.
For more troubleshooting and comparison guides, visit our comparisons section.
Key Takeaways
- Lowering the TTL before switching nameservers is the single most important preventive step; skipping it means errors can last 48 hours.
- Exporting and copying all DNS records (including MX and TXT) before the switch prevents email and other services from going dark.
- GoDaddy locks domains by default — unlocking and requesting the EPP Code are mandatory steps for any transfer.
- Inconsistent propagation (some users see the site, others don't) is normal and temporary — dnschecker.org lets you monitor it in real time.
- The correct sequence is: export → configure new host → lower TTL → wait → switch nameservers → monitor.
With proper planning, a GoDaddy domain migration can complete with no visitor-facing disruption. Need someone to manage the process for you? Reach out to the team at elenlace.com and we'll handle every step.
FAQ
How long does DNS propagation take after changing nameservers at GoDaddy?
With a low TTL (600 s), propagation can complete in 15-60 minutes. With a standard TTL (3600-86400 s), it can take 24 to 48 hours. Plan the migration for a low-traffic window.
Can I keep my Google Workspace or Microsoft 365 email working during the migration?
Yes, as long as you copy the MX and TXT records (domain verification, SPF, DKIM) to the new DNS provider before switching nameservers. Email won't be interrupted if the records are correct.
Is there a cost to transfer a domain out of GoDaddy?
A full transfer to another registrar typically requires paying one year of renewal at the new registrar (price varies). Changing only the nameservers — without moving the domain's registration — is free and much faster.
I confirmed the transfer but the domain is still at GoDaddy — what's happening?
Transfers take 5 to 7 business days to complete once both parties confirm. If GoDaddy sent a confirmation email and you didn't respond in time, the request is automatically canceled and you'll need to start over.
Useful resources
Other providers and guides worth comparing:
