Fix Server Not Found in WordPress After Hosting Change

If you see “Server not found” in WordPress right after changing hosting, the domain’s DNS records have not finished pointing to the new host, or the new server is not configured to accept your domain yet. This guide walks you through the exact steps to diagnose and fix the issue, from checking DNS propagation to updating your WordPress URLs.

Why “Server Not Found” Happens After a Hosting Move

When you change hosting, your domain name must be re-pointed to the new server’s IP address. This is done through DNS (Domain Name System) records, which act like a phonebook for the internet. Until those records update globally, your browser cannot find the server, hence the error. The delay can range from a few minutes to 48 hours, but it is usually under 24 hours. Other causes include an incorrect nameserver setting, a missing domain in the new host’s cPanel, or an SSL certificate that has not been issued for the new server.

Step-by-Step Fix: What to Do First

Check DNS propagation – Use a free online DNS checker (e.g., dnschecker.org) to see if your domain resolves to the new host’s IP. If it still shows the old IP, wait and re-check after a few hours.
Verify nameservers – Log in to your domain registrar (where you bought the domain) and confirm that the nameservers are set to the ones provided by your new host. If they are wrong, update them and wait for propagation.
Confirm the domain is added to the new server – In your new hosting control panel (cPanel, Plesk, etc.), ensure your domain is listed as an addon or primary domain. If not, add it.
Check the new server’s IP – Your new host should have sent you an IP address or a temporary URL. If you have that IP, you can temporarily edit your local hosts file to test the site before DNS updates globally.
Update WordPress URLs if needed – If you can access the site via a temporary URL, log in to wp-admin and go to Settings > General. Update the WordPress Address and Site Address to your real domain (e.g., https://example.com).
Re-issue SSL certificate – If you use HTTPS, ensure an SSL certificate is installed for your domain on the new server. Many hosts offer free auto-SSL via Let’s Encrypt.

How DNS Propagation Works (And Why It Takes Time)

DNS records are cached by internet service providers (ISPs) and local routers. When you change hosting, the old server’s IP remains cached until the TTL (Time To Live) expires. TTL values are set by your old host and can be as short as 300 seconds or as long as 86400 seconds (24 hours). Once the TTL expires, the DNS servers fetch the new records. This is why the error may persist for hours. You can speed up the process by lowering the TTL before the change, but if you’ve already moved, you just have to wait.

Common Mistakes That Cause the Error

Forgetting to update nameservers – Many people change hosting but leave nameservers pointing to the old host, so the domain never resolves to the new server.
Using the wrong IP address – Copy-pasting an IP from an old email or a different server can cause the site to point to the wrong place.
Not adding the domain to the new server – Even if DNS is correct, the new server must have a virtual host entry for your domain. Without it, the server returns a “Server not found” or a default page.
SSL certificate mismatch – If the SSL certificate is for the old server or not yet issued, browsers may block the connection, showing a similar error.
Editing the wrong DNS record – Some hosts use an A record (domain to IP) or a CNAME (subdomain to another domain). Mixing these up can break resolution.

How to Test If the Problem Is DNS or the Server

To isolate the issue, try accessing your site via the server’s IP address directly. If you get a “Site not found” or a default hosting page, the server is working but the domain is not configured. If you get a connection timeout, the server may be down or the IP is wrong. Another method is to use a tool like ping or nslookup from your computer. If the IP returned is the new host’s IP, DNS has propagated for you, and the problem is likely server configuration.

What to Do If DNS Is Correct but the Error Persists

If DNS checks show the correct IP and you’ve confirmed the domain is added to the new server, the issue might be with your local cache. Flush your local DNS cache (on Windows: ipconfig /flushdns; on Mac: sudo killall -HUP mDNSResponder). Also try a different browser or incognito mode. If the error continues, contact your new host’s support. They can check the virtual host configuration and ensure the domain is active. Sometimes, the host may have placed your site on a shared IP that is blocked by your ISP or region, but that is rare.

Frequently Asked Questions

How long does DNS propagation take after changing hosting?

It typically takes between 1 and 24 hours, but it can take up to 48 hours in rare cases. The exact time depends on the TTL set by your old host and how quickly your ISP updates its cache.

Can I see my WordPress site before DNS propagates?

Yes. Most hosts provide a temporary URL (like serverip/~username or a subdomain like temp.yourhost.com). You can use that to preview your site and even log in to wp-admin to update URLs.

Why does my site work on my phone but not on my computer?

This is usually due to different DNS caches. Your phone may be using a different DNS server (like 8.8.8.8) that has updated, while your computer’s ISP cache is stale. Flush your computer’s DNS or wait a bit longer.

Do I need to change my WordPress URLs after moving hosting?

Yes, if you were using a temporary URL or an IP address to access the site. Go to Settings > General in wp-admin and update both the WordPress Address and Site Address to your real domain. If you cannot access wp-admin, you can edit the wp-config.php file to define WP_HOME and WP_SITEURL.

What if my domain registrar is different from my hosting provider?

That is common. You need to log in to your registrar to change nameservers to the ones given by your new host. If your domain is registered with the same company as your old host, make sure you haven’t accidentally left the nameservers on the old host’s default.

Is it safe to delete the old hosting account after moving?

Wait until you have confirmed the new site works and DNS has fully propagated. Deleting the old account too soon can cause downtime if you need to retrieve files or databases. Keep the old account active for at least a week after the move.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →