View Single Post
  #1  
Old 18th October 2006, 05:17
Norman Norman is offline
HowtoForge Supporter
 
Join Date: May 2006
Posts: 242
Thanks: 0
Thanked 18 Times in 14 Posts
Default Issues with bind

My syslog spams these messages when bind restarts (fails).

Oct 18 04:09:12 bigfoot named[26716]: starting BIND 9.2.4 -u bind -t /var/lib/named
Oct 18 04:09:12 bigfoot named[26716]: using 1 CPU
Oct 18 04:09:12 bigfoot named[26716]: loading configuration from '/etc/bind/named.conf'
Oct 18 04:09:12 bigfoot named[26716]: /etc/bind/named.conf:32: zone '0.0.127.in-addr.arpa': already exists
Oct 18 04:09:12 bigfoot named[26716]: loading configuration: failure
Oct 18 04:09:12 bigfoot named[26716]: exiting (due to fatal error)

My named config looks as following:
zone "." {
type hint;
file "db.root";
};

zone "0.0.127.in-addr.arpa" {
type master;
file "db.local";
};

zone "40.115.217.in-addr.arpa" {
type master;
file "pri.40.115.217.in-addr.arpa";
};
zone "0.0.127.in-addr.arpa" {
type master;
file "pri.0.0.127.in-addr.arpa";
};


If I comment or remove :
zone "0.0.127.in-addr.arpa" {
type master;
file "db.local";
};

bind starts fine, but trouble returns everytime ispconfig re-generates named.conf .
Does anyone have an idea on how I can fix this?
__________________
http://www.xh.se
Reply With Quote
Sponsored Links