• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Setting up Nameservers

T

TechGuyAlabama

Guest
I have 2 ips from my host and I need to set them up for plesk. I have the initial install done, how do I setup the nameservers for these ips? Are the nameservers on Plesk setup at the Plesk admin level or the reseller level? Where do I set these up?

Thanks!
 
Resellers don't have a DNS template just the server wide template but you can also just configure DNS per domain. You can edit the server's main DNS template with your name servers but first you need to create a domain to hold your name servers.

So, if you want 'ns1.domain.com' and 'ns2.domain.com' create the domain 'domain.com' in Plesk and edit its DNS records so you have an 'A' record for ns1. and ns2. which point to the DNS IPs. (make sure domain.com points to your server) Once you do this 'ns1.domain.com' and 'ns2.domain.com' will start resolving and be ready for use.
 
Resellers don't have a DNS template just the server wide template but you can also just configure DNS per domain. You can edit the server's main DNS template with your name servers but first you need to create a domain to hold your name servers.

So, if you want 'ns1.domain.com' and 'ns2.domain.com' create the domain 'domain.com' in Plesk and edit its DNS records so you have an 'A' record for ns1. and ns2. which point to the DNS IPs. (make sure domain.com points to your server) Once you do this 'ns1.domain.com' and 'ns2.domain.com' will start resolving and be ready for use.

k ty that worked!
 
Back
Top