Changed Nameservers but Website Still Not Working?
Changing nameservers moves authority for your domain’s DNS. It does not automatically recreate every website, email and verification record that existed at the previous DNS provider.
1. Confirm the new nameservers
Check which nameservers are currently authoritative. Make sure they exactly match the values supplied by the new DNS or hosting provider.
2. Check the new DNS zone
The new provider needs the records required by your services. For a website this often means an A, AAAA or CNAME record. Email can require MX and TXT records, while other services may rely on verification records.
3. Check both root and www
example.com and www.example.com can be configured differently. Test both and ensure your hosting provider recognises whichever hostnames you intend to use.
4. Allow for caching
After a delegation or record change, some resolvers can temporarily retain older answers. Compare multiple resolvers before concluding that every visitor sees the same result.
5. Check hosting and SSL
If DNS points to the correct destination but the site still fails, inspect the HTTP response and certificate. The hosting platform may still need the custom domain added or verified, and HTTPS provisioning may follow DNS verification.
Check your domain
Use ZoneCheckr to inspect the live configuration before making changes.
Run Domain Health CheckStill stuck? Get technical help with your domain →