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

Question ACL reset in BIND breaks AXFR to secondary DNS

Medina

New Pleskian
Server operating system version
Debian 12
Plesk version and microupdate number
Plesk Obsidian Web Host Edition 18.0.70
Hello,
I’m experiencing an issue with the DNS service managed via Plesk. The primary server uses BIND, and the secondary server runs on PowerDNS.


Zones are created correctly on the primary server, and Plesk generates the following directive for zone transfers:


conf: /var/named/run-root/etc/named.conf

zones.PNG

However, the secondary server at IP 77.235.14.8 does not receive the zone transfers.

What I see in the BIND logs (journalctl -u named):

Jul 14 22:22:27 megahost.kg named[1334500]: client @0x7f22b8e6e168 77.235.14.8#51189 (14.235.77.in-addr.arpa): zone transfer '14.235.77.in-addr.arpa/AXFR/IN' denied
Jul 14 22:22:27 megahost.kg named[1334500]: client @0x7f22b8e6c168 77.235.14.8#34875 (73.62.92.in-addr.arpa): zone transfer '73.62.92.in-addr.arpa/AXFR/IN' denied
Jul 14 22:23:27 megahost.kg named[1334500]: client @0x7f22b8e70168 77.235.14.8#45755 (14.235.77.in-addr.arpa): zone transfer '14.235.77.in-addr.arpa/AXFR/IN' denied
Jul 14 22:23:27 megahost.kg named[1334500]: client @0x7f22ba5e9168 77.235.14.8#51291 (73.62.92.in-addr.arpa): zone transfer '73.62.92.in-addr.arpa/AXFR/IN' denied


At the end of /var/named/run-root/etc/named.conf , Plesk generates the following directive:
acl common-allow-transfer {
none;
};

I assumed that this is the reason for the transfer denial, because common-allow-transfer is referenced in the zone definitions.


So I manually changed it to:
acl common-allow-transfer {
77.235.14.8;
};


Unfortunately, after any action in Plesk (e.g., adding a new zone), the ACL gets automatically overwritten back to:


acl common-allow-transfer {
none;
};


Could you please advise:


  • Am I making the correct changes to solve the issue?
  • Or is there another recommended way to configure transfers to a secondary DNS server under Plesk?

Thank you very much in advance!
 
Via Tools & Settings > DNS settings > Transfer Restrictions Template tab
Thank you, I registered the IP of the secondary DNS as you recommended and the error "Jul 14 22:23:27 megahost.kg named[1334500]: client @0x7f22ba5e9168 77.235.14.8#51291 (73.62.92.in-addr.arpa): zone transfer '73.62.92.in-addr.arpa/AXFR/IN' denied" disappeared after your help, there is still a question: is it necessary to register also-notify { 77.235.14.8; };? so that the secondary DNS receives records? Until now, the secondary PowerDNS does not see new records.
 
Back
Top