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

named.conf file bug

C

choonkiat

Guest
Hi,

Extra lines (highlighted in red) will appear in the named.conf file whenever any DNS changes make by the plesk via the web interface.

A sample problem of the named.conf file (problem highlight in red).

zone "xxx.com" {
type master;
file "xxx.com";
allow-transfer {
xxx.xx.xxx.xxx;
xxx.xx.xxx.xxx;
common-allow-transfer;
};
};


common-allow-transfer;
};
};


zone "next_xxx.com" {
type master;
file "next_xxx.com";
allow-transfer {
xxx.xx.xxx.xxx;
xxx.xx.xxx.xxx;
common-allow-transfer;
};
};

After remove the line and restart named service. Then the DNS will work properly again.
Any advice on what is wrong?
 
Back
Top