Your website worked before the move. Now customers see an error, your phone loads the old homepage, and your laptop refuses to connect. If your business depends on bookings, inquiries, or online orders, that silence can feel expensive. The good news is that a hosting or DNS change does not automatically mean your WordPress site is broken. Often, one part of the connection still points to the wrong place.
Check the Route Before You Change WordPress.
- Confirm which nameservers manage your domain and whether the website records match your new hosting setup.
- Check that the new host has your website files, database, domain assignment, and HTTPS certificate ready.
- Clear relevant caches after correcting the cause, and send your host specific evidence if the problem continues.
Why a Hosting Move Can Interrupt Your Website
A visitor needs several things to line up before your homepage appears. Your domain needs working nameservers. Those nameservers provide DNS records that direct traffic toward your hosting service. The server then needs to recognize your domain, provide a valid SSL certificate for HTTPS, and load WordPress.
A hosting move changes part of that chain. A nameserver change may move responsibility for every DNS record to another provider. Updating an address record changes where website traffic goes, but it does not copy your WordPress files or database.
That distinction explains many outages. The domain might reach the new server before the website is ready. Alternatively, the website may be ready while visitors still receive the old address from a cached DNS response.
Work through the connection in order. Repeatedly changing unrelated settings makes it harder to identify what actually failed.
Start With the Exact Error and a Second Connection
Open your website and write down the complete error message. A browser that cannot find the domain suggests a different problem from a browser displaying a certificate warning. A database connection error means the request reached a server running WordPress, although you still need to confirm it is the intended server.
Test your main domain and its www version separately. Try HTTPS for both. A working address without www does not prove the www address is configured correctly.
Check through home or office Wi-Fi, then try mobile data. In the Philippines, your fixed internet connection and mobile carrier may use different DNS resolvers. Different results can reveal cached answers or a network-specific issue.
A private browser window can help rule out some browser state. It does not bypass your internet provider’s DNS cache.
What Different Symptoms Can Tell You
| What You See | Possible Cause | Useful Next Check |
|---|---|---|
| Domain cannot be found | Missing DNS records, incorrect nameservers, or cached lookup failures | Compare registrar settings and active DNS records with the intended setup |
| Old homepage appears | Old DNS answer or cached website content | Confirm which server receives the request before clearing website caches |
| Certificate or privacy warning | Missing, expired, or mismatched SSL certificate | Check certificate coverage for both domain versions |
| Hosting placeholder appears | Domain reaches a server without the correct website assignment | Ask the host to verify the domain mapping and website folder |
| Database connection error | Database settings, permissions, or database availability problem | Ask the host to check the migrated database and WordPress connection settings |
Confirm Which Nameservers Control Your Domain
Sign in to the company where your domain is registered. Find its nameserver settings. Compare those entries with the instructions for your intended DNS provider.
Your registrar, DNS provider, and hosting company can be three separate businesses. Moving WordPress to a new host does not always require changing nameservers. You may only need to update website records at your existing DNS provider.
If you did change nameservers, the new DNS provider needs a complete copy of the records your services require. The new host may create website records automatically, but it may not recreate records for business email, verification services, or other subdomains.
Before editing anything, save screenshots or export the current DNS zone if that option is available. Keep the old hosting account active until the migration is verified. This preserves a reference and reduces the chance of losing access to files you still need.
Inspect DNS Records Before Making More Changes
At this point, inspect what a DNS lookup currently returns. Running a DNS report lets you review address, nameserver, mail, and other record information before changing settings. Treat the results as one resolver’s view. They do not prove that every network sees the same answer or that the website itself works.
Compare the returned information with the exact values supplied by your hosting or DNS provider. Edit records where your active nameservers are managed. Changing records in an unused hosting dashboard will have no effect on public traffic.
- A record: Check that the main domain uses the IPv4 address required by your current hosting setup.
- AAAA record: Verify that any IPv6 address belongs to a working service for your website. An outdated entry can send some visitors to the wrong server.
- www record: Confirm that its CNAME or address record follows your provider’s instructions. The main domain and www need separate DNS coverage.
- Email records: Preserve required MX and TXT records, including email authentication settings, when moving DNS management.
If you use a content delivery network or DNS proxy, public address records may show that service’s addresses instead of your hosting server’s address. Check its origin settings before assuming the public result is incorrect.
DNS caches follow record lifetimes, often called TTLs. Previously cached answers may remain until their existing lifetime expires. Lowering a TTL after the change does not shorten an answer already stored elsewhere.
Waiting helps only when the published configuration is correct. A wrong address does not fix itself with time. If lookups fail after a nameserver change despite apparently correct records, ask your DNS provider to check delegation and DNSSEC. An old DNSSEC record at the registrar can prevent validating resolvers from accepting the new setup.
Make Sure the New Host Can Serve Your Domain
Correct DNS can still lead to an empty hosting account. Open your new hosting dashboard and confirm that your domain is attached to the migrated website.
The host needs your WordPress files and database. It also needs the correct website folder and database connection details. A migration tool reporting success is useful, but a working preview provides stronger evidence that the copy loads.
Use a hosting preview feature if your provider offers one. Some previews have limits with HTTPS, redirects, or WordPress URLs, so ask support how to test the site accurately before public traffic settles.
A placeholder page, persistent server error, or database error is a good reason to contact the host immediately. Ask whether the domain reaches the correct account and whether the migration completed. There is little benefit in waiting for DNS caches to expire if the destination server cannot serve the site.
Check SSL Before Forcing HTTPS
Your previous host’s SSL certificate does not automatically become available on the new server. The new host must install or issue a valid certificate covering the addresses visitors use.
Look for an SSL or security section in your hosting dashboard. Check the certificate status, expiration date, and covered names. If customers use both the main domain and www, both need valid coverage when accessed over HTTPS.
Certificate issuance may depend on domain validation. Incorrect DNS, blocked validation requests, or certificate authority restrictions can prevent issuance. Ask the host for the actual validation error if the dashboard only says that setup failed.
Do not bypass a browser’s privacy warning to test customer payments. Get HTTPS working before asking visitors to submit passwords or order details.
If the site reports too many redirects, check whether WordPress, a security plugin, the hosting panel, and a proxy are applying conflicting HTTPS rules. Ask the host to verify proxy settings and redirect behavior before changing several controls at once.
Clear WordPress Caches After the Connection Works
Caching becomes the next suspect once DNS points to the intended service and HTTPS works. WordPress page caches, hosting caches, a content delivery network, and your browser can each retain older content.
Clear the cache in your WordPress caching plugin, then purge the hosting cache and any content delivery network cache. Finish by refreshing your browser or testing in a private window.
A cache plugin cannot repair missing DNS records or an invalid certificate. Purging it repeatedly during those failures will not restore the connection.
If WordPress redirects visitors to a temporary address or the previous domain, check the WordPress Address and Site Address settings. A hosting move that keeps the same domain usually does not require changing these URLs. If you cannot reach the dashboard, ask support to inspect the stored values and any configuration overrides.
For an actual domain change, old URLs may also remain in the database. Use a WordPress-aware migration process with a backup. Broad manual replacements can damage stored plugin or theme settings.
Give Your Hosting Provider Evidence They Can Use
Contact support as soon as the problem requires access to server settings, certificate issuance, logs, or migration details. You do not need to exhaust every possible fix first, especially when customers cannot place orders.
A specific support request saves time. Send the information you have already gathered, keeping passwords and private keys out of screenshots.
- The affected domain and whether the main address, www, or both fail.
- The exact browser error and a screenshot showing the address bar.
- When you changed hosting, nameservers, or DNS records, with your time zone.
- The expected hosting address and the DNS results you observed.
- Whether Wi-Fi and mobile data produce different results, plus which caches you cleared.
Ask the host to confirm domain mapping, migration status, SSL coverage, and relevant server errors. If your registrar or a separate DNS provider controls the failing setting, the host should help identify which provider needs to act.
Bring Customers Back to a Working Website
After the homepage returns, test the tasks your business relies on. Open service pages, submit a contact form, check booking availability, and verify checkout using your payment provider’s test process where available. Confirm that form notifications arrive.
Test again on a phone through mobile data. Check both domain versions and confirm that redirects end at your preferred HTTPS address without warnings.
A hosting move is finished when customers can use the site reliably. By checking nameservers, DNS records, the destination server, SSL, and caches in that order, you give each symptom a clear next step. That makes recovery less stressful and gives your hosting provider something concrete to fix.