• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • 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.

DNS zone transfers allowed networks

T

trix@

Guest
When migrating BIND zone files into Plesk it does not pick up the IP address/mask value we have set in Plesk to allow networks "to get a copy of DNS zone."

Is there a command line option to add an allowed network to the Zone Transfer tab under DNS Settings? We need to automate this using a script as we have several thousand DNS BIND files to import.

Thanks.
 
We worked around this by using an SQL query:

insert into misc (param, val) VALUES ('DNS_Allow_Transfer1', '1.2.3.4/24');

The "1" after Transfer1 can be changed to add other zones, e.g. DNS_Allow_Transfer2
 
Back
Top