DNS edits can affect the website and email separately. A change to the root address does not guarantee that the www address still reaches the same site.
What to check
- Document the current DNS records
- Confirm the intended hosting destination
- Check both root and WWW responses
What the results mean
Compare current records with the intended host and preserve the previous values. Correct only the affected records, then check both website names and email.
Trace the active destination
Record the active nameservers and the A, AAAA, and CNAME records for both the root domain and www. A record pointing to an old server can make some addresses load the wrong site. Test the intended host directly where possible and compare its configuration with the public response before editing more records.
Change only what the move requires
A DNS zone can also hold email and verification records. Replacing the whole zone to fix the website may break unrelated services. Keep a copy of the prior values, update the records that actually route the site, and verify the SSL certificate and redirects after the public address resolves to the destination.
Why can different visitors see different results?
Resolvers can retain earlier answers for a time. Compare results from more than one network and account for the record's cache setting. If results still differ later, confirm that the authoritative zone and all intended nameservers agree.
Greg Grigorian
For hosting trouble, migrations, backups, or a site that stopped working, get a clear diagnosis and a tested recovery path. Greg can review the setup and handle the work.