Is this your problem?
- The site stopped loading for everyone right after a host move or nameserver change
- "This site can't be reached", a blank page, or the old host's "account suspended" or default page
- It loads from some places and not others, or flips between the new site and an error
- Email on the domain broke at the same time, which points at DNS records
- A security warning appears because the new server has no certificate yet
What usually causes it
How to tell: A nameserver or record change spreads across the internet over hours. Until it finishes, visitors are split between old and new.
How to tell: The A record or the nameservers were set to the wrong value, so visitors are sent nowhere useful.
How to tell: The files or database were not fully copied, so the new server has nothing to show.
How to tell: https worked on the old host but no certificate was issued on the new one, so secure requests fail.
How to tell: Visitors still hitting the old server during propagation see a suspended or blank page.
Before you touch anything
- Write down the new server address (the A record IP) and the nameservers you set, so you can check them.
- Confirm with the new host that the files and database are fully in place and the site loads on a temporary URL they provide.
How to fix it, step by step
-
1
Check where the domain points now
Use a DNS lookup or a propagation checker and enter your domain. It shows the address the world is seeing, and whether it matches the new server. If it is split, propagation is still in progress.
-
2
Make sure the records are correct
In your DNS or domain panel, confirm the A record points at the new server IP, or the nameservers are the new host's. A typo here sends everyone nowhere.
-
3
Confirm the new server actually has the site
Ask the new host for a temporary URL, or edit your own hosts file to point the domain at the new IP, and load it. If it works that way, the site is in place and you are only waiting on DNS.
-
4
Issue the certificate on the new server
If https fails, issue a free Let's Encrypt or AutoSSL certificate on the new host for the domain. It can usually only be issued once DNS points at the new server, so this sometimes has to wait for propagation.
-
5
Lower the TTL next time, and wait this time
Propagation follows the record TTL. There is little to do now but wait, usually a few hours, up to a day or two, while watching the propagation tool. For a future move, lower the TTL a day ahead so changes spread faster.
-
6
Keep the old host live until it finishes
Do not cancel the old hosting until the propagation checker shows the new address everywhere, so no visitor lands on a dead server.
Stop and get help if
- The propagation checker shows the new address everywhere but the site still fails, which means the new server or its certificate is the problem, not DNS.
- The move involves a shop or email that cannot be down, and you are not sure the records are right.
- DNS and records look correct but the new host shows nothing, which means the copy did not complete.
Stop it happening again
- Lower the record TTL a day before a planned move so changes spread quickly.
- Set up the site, and its certificate, on the new server and test it on a temporary URL before you switch DNS.
- Keep the old host running until propagation is fully complete.
- Move email (the MX records) deliberately, since a nameserver change moves it too.
Questions people ask
How long does propagation take?
Often a few hours, sometimes up to 24 to 48 hours, depending on the record TTL and the networks in between.
Why does it work for some people and not others?
Different networks update at different times. Some already see the new server; some still hit the old one until their cache refreshes.
Did I lose my site?
Almost never. The files and database are on one server or the other. The usual problem is only that the address has not finished spreading.
My email broke too. Why?
Changing nameservers moves every record, including email (MX). The email records have to be set on the new DNS as well.