• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Pointing a domain to a different host not resolving to other host

pfriedl

New Pleskian
Hi all. OK, so I created an account and set up a domain pointing to my nameserver so that I can use it for email, but I want the domain to point to GoHighLevel servers for the actual web pages.

I've got the A record for the domain pointing to their IP address, and the CNAME record for www.my-domain.com pointing to their server as well and can confirm the DNS records are correct.

However, the domain is still resolving to the Plesk starter page for the account and not to the target host.

How can I set this up so that the web side of things is hosted elsewhere, or is there a cache setting that needs to be refreshed, or?
 
It usually takes a while before any DNS change are propagated. Depending on the TTL setting of your DNS records this can take anywhere from 1 minute to 1 week, but it is usually less than 24 hours. DNS Checker - DNS Check Propagation Tool is a use full tool to see if your DNS records have been propagated.
 
Back
Top