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

wrong allow-transfer ip address

S

sofferto

Guest
hi,

i have changed the ip address of my plesk for linux 8.0.1 that is my primary dns server.

Also the secondary dns server ip address is changed.

But now, when i create a new domain in plesk, in the NAMED zone file (named.conf)
plesk set the SECONDARY allow-transfer ip address so wrong while the PRIMARY it's right.

Example:

my OLD ip address are:

primary: 100.100.100.1
secondary: 100.100.100.2

my NEW ip address are:

primary: 101.101.101.1
secondary: 101.101.101.2

The zone file is:

zone "mydomain.com" {
type master;
file "mydomain.com";
allow-transfer {
101.101.101.1;
100.100.100.2;
common-allow-transfer;
};
};

Every time i create a new domain in plesk i must change the secondary allow-transfer ip address manually.

Can you help me to fix this problem?

thanks
 
Back
Top