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

Slave DNS Manager - Slave zone location

Chris1

Regular Pleskian
Hello,

Is it possible to change the location that the Slave DNS Manager adds slave zones to on the slave DNS servers?

Currently it put it in /var/named but I would like them to go into /var/named/slaves.

Instead of this being issued by the Plesk server:
Code:
/usr/sbin/rndc -c slave.config addzone example.com '{ type slave; file "example.com"; masters { <plesk_ip>; }; };'

It would need to be this:
Code:
/usr/sbin/rndc -c slave.config addzone example.com '{ type slave; file "slaves/example.com"; masters { <plesk_ip>; }; };'

The directory owner for /var/named keeps changing back to "root" instead of "named" after a BIND update which prevents zones from being created on the slave servers.
 
Last edited:
Back
Top