DNS Propagation Checklist After Domain Changes
Updated: April 21, 2026 ยท By Website Checker editorial team
DNS propagation is often blamed for every launch issue. In reality, many incidents are record mistakes, nameserver mismatches, or missing web server config. Use this checklist to separate those cases.
What actually propagates
- A/AAAA records: where your domain points
- CNAME: alias target changes
- MX/TXT: mail and verification records
- Nameserver changes: authority transfer at registrar level
Expected timing
Many updates appear within minutes, but full global convergence can take longer depending on TTL values and resolver caches. Nameserver changes can take longer than a simple A record update.
Checklist
- Confirm the authoritative DNS provider is the one you edited.
- Verify record name and target (avoid accidental apex/www mismatch).
- Check TTL value and whether old caches may still be valid.
- Run the domain in Website Checker for objective resolution status.
- Test both `example.com` and `www.example.com` if relevant.
Common mistakes
- Pointing DNS correctly but forgetting virtual host/server block config.
- Creating records at the wrong zone level.
- Only configuring IPv4 while clients reach via stale IPv6.
- Confusing registrar DNS with CDN DNS panel.
If DNS resolves but your site still fails with 5xx responses, continue with our 5xx troubleshooting guide.