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