• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

How to point a domain to Plesk enabled server the right way?

LennardF1989

New Pleskian
Hello,

I recently bought a domain (lennardf1989.com), but I just can't get it to work right.

I was wondering what how I would point my domain to a Plesk server so that I have all functionality (mail, DNS, subdomains). I have to do this in my suppliers DNS management, since the Plesk server I want my domain on has no nameserver (or is this normal?).

WHat I have now is:

lennardf1989.com. A <ip>
mail A <ip>
lennardf1989.com. NS ns1.splintercellnetwork.com.
lennardf1989.com. NS ns2.splintercellnetwork.com.
mail MX 10 //This will aim it to the above A mail record
* CNAME lennardf1989.com.

But for some reason most subdomains don't work, it seems like only the partial Plesk DNS settings are taken into account.

Could someone help me and show how they setup their domain from a supplier to piont to a Plesk server?

Best regards,
Lennard Fonteijn

Ps. Is it true a Plesk server doesn't have a nameserver on its own? If it would, then the DNS in the Plesk account would be the Primary.

Edit: Or are those DNS settings supposed to be alright?
 
Back
Top