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

bind fails to start, two entries of zone "0.0.127.IN-ADDR.ARPA"

B

Billythekid@

Guest
We have a customer which have this error, it's pretty much a default installation under debian, he added one domain and when it didnt take he checked the log and it said bind couldnt start because of:

named[7469]: /etc/named.conf:138: zone '0.0.127.in-addr.arpa': already exists previous definition: /etc/named.conf:80
named[7469]: reloading configuration failed: failure


here are the two zones created by PLESK

/* zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "localhost.rev";
};

which I've commented out to get it to start...

and this one:

zone "0.0.127.in-addr.arpa" {
type master;
file "0.0.127.in-addr.arpa";
allow-transfer {
common-allow-transfer;
};
};


Does anyone know of this? why does this happen? bug?

Thanks in advance
Billy the kid
 
Back
Top