DNS Propagation Troubleshooting Checklist
DNS propagation problems can make a website appear broken even when the server is healthy. Users in different locations may see different IPs, old hosting, NXDOMAIN errors or SSL issues during DNS changes.
Core principle
DNS is a distributed system. When you change records, the world does not update instantly. Always confirm which resolver sees which value before changing server settings.
Checklist
- Confirm you edited DNS at the correct provider.
- Check nameservers for the domain.
- Check the A record value.
- Check www record if used.
- Check TTL value.
- Query multiple DNS resolvers.
- Check whether Cloudflare proxy is enabled.
- Confirm Nginx has a matching server block.
- Wait for propagation when needed.
- Install or renew SSL only after DNS points correctly.
Reusable lesson
Many SSL and connection errors during migration are really DNS state problems. Prove DNS first, then debug the server.
When to Use This Checklist
Use this checklist after changing domain DNS, moving a website to a new VPS or debugging inconsistent domain behavior.
Required Tools
Domain registrar, DNS manager, VPS IP, DNS checker, dig, Cloudflare if used, Nginx access
Before You Start
Know which DNS provider is authoritative for the domain before editing records.
Structured Checklist Steps
- Check nameservers.
- Confirm DNS provider.
- Check root A record.
- Check www record.
- Check TTL.
- Query public resolvers.
- Check Cloudflare proxy.
- Check Nginx server block.
- Wait if needed.
- Install SSL after DNS is correct.
Verification Steps
- Domain resolves to expected IP.
- www behavior is known.
- Authoritative nameservers are correct.
- Nginx matches the domain.
- SSL can be issued successfully.
Rollback Plan
If DNS points to the wrong IP, restore the previous record or update to the correct VPS IP and avoid making unrelated server changes while propagation completes.
Common Mistakes
- Editing DNS at the wrong provider.
- Forgetting nameservers.
- Testing only one resolver.
- Installing SSL before DNS is ready.
- Confusing Cloudflare proxy IPs with origin IP.
Related Commands
dig example.com
dig www.example.com
dig NS example.com
dig @8.8.8.8 example.com
dig @1.1.1.1 example.com
curl -I http://example.com