Introduction
When a site stops loading after a DNS change, the root cause is often one of three things: the record points to the wrong place, the nameserver cutover was incomplete, or the destination server was not ready when traffic arrived. Waiting helps only when the underlying change is correct.
Symptoms
- The outage started immediately after editing DNS records
- The domain resolves to a new IP but the site still does not load correctly
- Some users see the old site while others see an error or timeout
- Email, CDN, or subdomain services break at the same time as the main site
- Dashboards show the new DNS values but live traffic still fails
Common Causes
- The new A or CNAME record points to the wrong destination
- Nameservers changed before the full zone was recreated
- The origin server is not listening, lacks the right virtual host, or rejects the hostname
- Old and new DNS providers both serve partial or conflicting answers
- Caches, CDN settings, or SSL configuration were not updated for the new endpoint
Step-by-Step Fix
- Query the authoritative DNS and verify the exact live answer for the hostname you changed.
- Confirm the destination IP, load balancer, or target hostname is the correct live infrastructure for the site.
- Test the destination directly to ensure the server is ready to serve the domain once DNS points to it.
- Compare registrar nameserver delegation with the provider where the zone currently exists.
- Review related records such as
www, apex, mail, and verification records so the migration is not only partially complete. - Check SSL certificates, virtual host bindings, and CDN settings on the new destination if DNS now resolves but page delivery still fails.
- Roll back the DNS change only if the previous endpoint is confirmed healthy and the rollback path is safer than finishing the fix.
- Re-test from multiple public resolvers and browsers until the site loads consistently.
- For future DNS changes, validate the target stack before moving live traffic and lower TTLs in advance.