Why is my domain not resolving after I changed DNS?
Common causes
The most common reason is propagation delay. When you change DNS records or nameservers, caches around the world still hold the old information until their TTL expires. This can take minutes to 48 hours. If you just made the change, it's likely still propagating.
Another cause is misconfigured records. If you switched to new nameservers but didn't recreate your A, CNAME, or other records at the new DNS provider, the domain won't resolve. Typos in IP addresses or hostnames also break resolution. Additionally, if you set a CNAME at the root domain, it may not work with some providers.
Troubleshooting steps
First, verify your DNS records using a tool like dig or an online DNS checker. Query your domain against multiple public resolvers (e.g., 8.8.8.8, 1.1.1.1) to see if they return the correct records. If they don't, the issue is at your authoritative nameservers or with propagation.
Next, flush your local DNS cache. On Windows, run 'ipconfig /flushdns'; on macOS, use 'sudo killall -HUP mDNSResponder'; on Linux, restart nscd or systemd-resolved. Also try a different network or device to rule out local caching. If the domain still doesn't resolve after 48 hours, contact your DNS provider or registrar.
- Check propagation with whatsmydns.net or dig.
- Verify records at your DNS provider.
- Flush local DNS cache.
- Try a different device or network.
- Contact support if issues persist beyond 48 hours.
Common mistakes
- Panicking immediately; propagation can take time, especially for nameserver changes.
- Forgetting to recreate all DNS records after switching nameservers.
- Overlooking local DNS cache, which can show old results even after propagation.
