Domain points to the wrong website: Common causes and solutions

A domain can point to a wrong website for various reasons. Sometimes the old website still appears, sometimes the main domain is displayed instead of a new addon domain, sometimes a default page or a completely unexpected installation is shown. It is important to check in a structured manner: Is the domain reaching the correct server? Is it correctly configured in cPanel? Does it point to the correct folder? Are there any redirects?

This article guides you step by step through the most common causes and shows you which points you should check before making any changes.

1. DNS points to the wrong server

The most common cause is an incorrect DNS record. If the A record or AAAA record points to an old or incorrect server, the request does not reach your current CURIAWEB hosting. Consequently, cPanel cannot deliver the correct website either.

Check:

• which nameservers the domain uses,
• which A record is set for the main domain,
• whether an outdated AAAA record exists,
• whether www is correctly set up via CNAME or A record,
• whether DNS propagation is still running.

If the domain does not point to the IP address of your CURIAWEB server, the DNS configuration must be adjusted at the authoritative DNS provider.

2. Domain has not been created in cPanel

Even if the DNS points correctly to the server, the domain must be created in the cPanel account. Otherwise, the web server does not know which website belongs to this domain. In this case, a default page, another website, or an error message may appear.

Checking in cPanel

1. Log in to cPanel.
2. Open the Domains section.
3. Check whether the affected domain appears in the list.
4. If not, click on Create A New Domain.
5. Create the domain with the correct Document Root.

3. Incorrect Document Root

The Document Root is the folder from which the website files are loaded. If the domain points to the wrong folder, the wrong website will be displayed.

Example: The domain newproject.ch is supposed to display its own website but points to public_html/. However, the main website is located there. In this case, the main website appears instead of the new project.

Typical Document Root errors

• Addon domain accidentally connected to the main domain folder,
• Alias domain created instead of a standalone domain,
• Website files uploaded to the wrong folder,
• WordPress installed in the wrong directory,
• Document Root changed afterwards, but files were not moved.

4. Alias domain created instead of an independent website

If the option Share document root with main domain remains enabled when creating a new domain, the new domain will use the same folder as the main domain. As a result, it can display the same website.

This is correct if a domain is to be used as an alias. However, if you want to run an independent website, the domain must be given its own Document Root.

5. Redirects or .htaccess rules

A domain can point correctly to the right folder and still redirect to another website. The cause is then often redirects in cPanel, rules in the .htaccess file, or settings in a CMS such as WordPress.

Check:

• cPanel Redirects section,
• .htaccess file in the Document Root,
• WordPress plugins for redirects,
• Theme functions or security plugins,
• CDN or proxy rules,
• Redirects at the external domain provider.

6. Incorrect WordPress URL or CMS address

In WordPress and other CMS systems, the website can be internally configured to a specific domain. For example, if WordPress still has olddomain.ch saved as the website address, the new domain may automatically redirect to the old address.

For WordPress, check:

• WordPress Address,
• Site Address,
• Redirect plugins,
• Cache plugins,
• Entries in the database,
• Configuration in wp-config.php.

7. Browser, DNS, or CDN cache

Sometimes the configuration is already correct, but your browser, your DNS resolver, or a CDN still shows old data. Therefore, you should always take cache effects into account when troubleshooting.

Test:

• Private browser window,
• Different browser,
• Different network, for example mobile data,
• DNS check via external tools,
• Clear cache in CMS or CDN,
• Flush local DNS cache, if necessary.

Systematic Error Analysis

1. Check which nameservers the domain uses.
2. Check A and AAAA records.
3. Check whether the domain is created in cPanel.
4. Check the Document Root.
5. Check whether files are in the correct folder.
6. Check redirects in cPanel.
7. Check .htaccess.
8. Check CMS settings.
9. Check SSL and HTTPS redirects.
10. Test via different networks.

When should CURIAWEB support help?

Contact CURIAWEB support if you cannot identify whether the problem lies with DNS, cPanel, Document Root, redirect, or CMS. Specify as precisely as possible which domain is affected and which website is displayed instead.

The following are helpful:

• Affected domain,
• Expected target website,
• Website actually displayed,
• Time of the last DNS change,
• Information about WordPress or CMS,
• Indication of whether external DNS providers or Cloudflare are used.

Frequently Asked Questions

Why does my new domain show the main website?
Usually the Document Root was shared with the main domain. For an independent website, the domain requires its own Document Root.

Why do I still see the old website?
Often, DNS records still point to the old server or DNS caches have not yet been updated.

Why does the domain always redirect to another domain?
Check cPanel redirects, .htaccess, WordPress settings, and external redirects.

Why is only www affected?
The www variant has its own DNS or redirect settings. Check CNAME, A record, and redirects.