If your domain opens the wrong website, shows a parking page, or does not load at all, start outside WordPress. DNS and hosting assignment decide which server receives the visitor before WordPress can do anything.
The quickest safe path is:
- Confirm the WordPress site works on your host's temporary or preview URL.
- Check which nameservers are active for the domain.
- Compare the public DNS records with the values from your hosting dashboard.
- Make sure the domain is attached to the correct WordPress site in hosting.
- Check any CDN or proxy, such as Cloudflare, if it manages DNS.
Do not reinstall WordPress, change themes, or edit plugins to fix a domain that is not reaching the right server.
Check whether WordPress works on the host
Test these separately:
example.comwww.example.com- Your host's temporary or preview URL
/wp-admin/on the temporary or preview URL
If the temporary URL loads WordPress but the domain does not, the problem is usually DNS, the hosting domain assignment, redirects, or a CDN.
If the temporary URL also fails, open the hosting dashboard first. Look for a stopped site, failed migration, server error, expired plan, or incomplete WordPress install before editing DNS.
Find the correct domain settings in your hosting account
Open your hosting control panel and look for its domain connection instructions. The values may include:
- Nameservers to enter at the registrar
- An
Arecord for the root domain - A
CNAMErecord forwww - An
AAAArecord for IPv6 - A verification record required by the host
Use the values shown for your specific site. Do not copy an IP address or nameserver from a general tutorial, because hosts often use different destinations for different accounts or data centers.
Before changing DNS, export the current DNS zone if your provider offers that option, or copy the existing records into a note. Nameserver changes and deleted records can affect email, verification services, subdomains, analytics, and third-party tools.
Confirm where DNS is managed
The active nameservers decide which DNS dashboard matters. If the domain uses your host's nameservers, edit DNS at the host. If it uses the registrar's nameservers, edit DNS at the registrar. If it uses Cloudflare or another DNS provider, edit records there.
Records added in the wrong dashboard will not affect public DNS.
Use Google Admin Toolbox Dig to check the public NS, A, AAAA, and CNAME answers. Compare them with the values shown in your registrar and hosting dashboard.
When replacing nameservers, make sure the new DNS zone already contains any required MX, TXT, and service records. Cloudflare's documentation on nameservers and DNS setups is useful if Cloudflare is part of the setup.
Fix the root and www records
Check both versions of the domain:
example.comwww.example.com
A common setup looks like this:
| Name | Type | Destination |
|---|---|---|
@ |
A |
IP address supplied by the host |
www |
CNAME |
Root domain or hostname supplied by the host |
Your host may require something different. Follow the host's instructions for your account instead of assuming every WordPress site uses the same record type.
Look for old or conflicting records, especially after a migration:
- Multiple
Arecords sending one hostname to different servers - An outdated
AAAArecord for IPv6 traffic - A parked-domain
CNAME - Registrar URL forwarding
- Records from a previous host
- A
wwwrecord pointing somewhere different from the root domain
Remove a record only after confirming it is not still needed. Avoid touching mail-related MX, TXT, or CNAME records while fixing the website destination.
Make sure the domain is attached to the right WordPress site
DNS may point to the correct server while the server still shows a parking page, default page, or a different website. That usually means the hosting account has not mapped the domain to the intended WordPress installation.
In your hosting dashboard, confirm that the domain:
- Is assigned to the correct WordPress site
- Is not parked or attached to another site
- Uses the correct document root
- Is listed as the primary domain or accepted alias
- Does not have an unwanted redirect
On cPanel hosting, the Domains interface shows domain mappings, document roots, and redirects. Other hosts usually place similar controls under Domains, Sites, or Domain Management.
If your hosting dashboard does not show these details, ask the host to verify the domain assignment or web-server virtual host.
Check Cloudflare or another proxy
If Cloudflare or another CDN manages the domain's nameservers, update the active DNS records there rather than at the registrar's DNS editor.
Check that each web record points to the current origin IP address or hostname from your host. An old origin can keep sending visitors to the previous server even when the nameservers are correct.
For Cloudflare, a proxied record returns Cloudflare IP addresses publicly while Cloudflare sends web traffic to the configured origin. Its proxy status documentation explains the difference between proxied and DNS-only records.
Temporarily switching a web record to DNS-only can help separate an origin problem from a proxy problem. Record the original setting first and restore it after testing, because DNS-only mode exposes the origin address and bypasses CDN protections.
Allow cached DNS answers to expire
DNS resolvers cache records according to their time to live, or TTL. After you correct a record, some networks may continue showing the old result until the cached answer expires.
Check the current public answer with a DNS lookup tool and compare it with the authoritative DNS dashboard. Avoid repeatedly changing a correct record, because each extra edit makes troubleshooting harder.
Cloudflare's TTL documentation explains how long records may be cached in its DNS. If Google Public DNS still returns an old answer after the authoritative records are correct, Google provides a cache flush tool.
Testing on mobile data or another network can also show whether stale DNS is limited to one resolver or device.
Check WordPress URLs only after DNS reaches the site
Once the domain reaches the intended WordPress installation, open Settings > General in wp-admin. Confirm that WordPress Address (URL) and Site Address (URL) use the intended domain and protocol.
Do not change these fields just because DNS is wrong. If the domain points elsewhere, changing WordPress URLs can make the dashboard harder to access without fixing the real problem.
For a migration or domain change, follow the official WordPress migration instructions. Back up the database before replacing URLs. Avoid plain database-wide text replacement because it can damage serialized data; use a WordPress-compatible migration tool or a careful search-replace method.
Configure HTTPS after the domain routes correctly
A certificate warning can mean the domain now reaches the new host, but the SSL certificate has not been issued there yet.
First confirm that every hostname you use, including www if enabled, reaches the intended server. Then issue or renew the certificate through the hosting dashboard. Enable forced HTTPS only after the certificate is valid for every hostname that redirects to HTTPS.
If the certificate tool fails, the host may still be seeing old DNS answers, the domain may not be attached to the site, or one hostname may point somewhere else.
Contact the right provider
Contact the registrar when:
- A nameserver change cannot be saved
- The domain is expired, suspended, or locked
- Public nameservers do not match the registrar setting
Contact the DNS provider when:
- The active DNS dashboard does not show the records you expect
- Public DNS still returns old records after the TTL should have expired
- CDN or proxy settings are sending traffic to the wrong origin
Contact the host when:
- DNS reaches its server but shows a parking page or the wrong website
- The server says the domain is unrecognized
- The domain assignment or document root cannot be corrected
- SSL cannot be issued after DNS reaches the host
Include the domain, current public NS, A, AAAA, and CNAME answers, plus the destination values shown in your hosting dashboard.