• 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.

Dns

P

poke

Guest
Hello,
I have a question regarding name server setups.

Instead of using enom's register name server feature, can I just use their name servers and create A records to point to ns1.domain.com ns2.domain.com?

Is this considered the wrong way to do this? I'd like to use enom domain features as well as point my domains using A records. You can only use the extra enom features when you're using their nameservers.

TIA,
poke
 
what's the point ? you won't be using n1.yourdomain.com and ns2.yourdomain.com

You'll be using ns1.name-services.com and 4 others that belong to enom to control your DNS

The point of using Enom's register name server is to point the domain to your Plesk servers for DNS queries.

So you need to decide if your going to use Enom or your own Plesk servers as the name servers.
 
Back
Top