The domain shows another website, the wrong content or redirects to another domain

If a domain opens another domain's website, an old installation or the server's default content, first find out where the request is being diverted: DNS, domain settings, directory, redirect, application or cache.

1. Check which server it points to

Look up the A and AAAA records publicly. If they point to another provider or a previous IP, fix the authoritative DNS zone and wait for propagation. Editing cPanel does not change the result while the domain still points to another server.

If the domain only uses the DNS zones tool

When the domain has no hosting and uses our zones tool, the A record may point to the zones server and show its default content. In that setup this is not necessarily a fault: if the aim is to open another website, you normally need to set up a domain redirect, not add the domain to a cPanel account.

2. Check the domain's directory

In cPanel, open Domains and check the associated document root. Two domains can serve the same files when they share public_html or the second one was added with Share document root. The application may still respond differently depending on the requested domain.

If they need to work independently, give the domain its own directory and put its files there. The guide to managing and configuring domains explains how to check and change that path.

3. Look for redirects

Check the Redirects section in cPanel and the .htaccess file in the directory. An old rule can send all visits to another domain even if DNS and the folder are correct.

Test temporarily without the browser cache, CDN or caching plugin. A 301 redirect can stay cached after you fix it.

4. Check the application URL

WordPress and other CMSs store their domain in the database. If the application keeps the old URL, it may redirect to it or load resources from the other website. In WordPress, check home and siteurl by following the guide Change the WordPress domain or URL.

Also check multisite settings, the canonical URL, environment variables and the framework's own redirects.

5. Confirm the public result

Clear caches only after fixing the cause, and test:

• The domain with and without www.
• HTTP and HTTPS.
• An internal path that was not cached.
• Another network or device.

If the domain points to the correct server and cPanel links it to the right directory, but the content served still does not match, contact support with the domain and the exact URL you expected to see.

Tell wrong content apart from a redirect

If the address in the browser changes, keep each redirect code and its Location header. If it stays the same but the content changes, check the domain association, the application and the cache key used by the proxy or CDN.

A DNS record cannot redirect to a path such as /tienda on its own: DNS resolves names, while an HTTP redirect is performed by a web service. If you need an independent website, assign it its own hosting and document root; if you only need to send visitors to another URL, use a redirect service that also handles HTTPS for the source domain.