• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

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