Thank you Doug,
This is the first thing i did
Code:
//include "/etc/bind/rndc.key";
include "/etc/bind/named.conf.options";
include "/etc/bind/named.conf.local";
include "/etc/bind/named.conf.default-zones";
But the result is still the same. Further to be sure if there could be a firewall issue I purged it, but nothings changed....
I will resume here the steps that I followed during installation:
- apt-get purge appmor
- apt-get install nscd
- apt-get install dhcp3-server
- apt-get install bind9 dnsutils
- rndc-confgen -a
I configured dhcp and it works correctly.
I configured bind, I will list here my files:
1. named.conf:
Code:
// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/doc/bind9/README.Debian.gz for information on the
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/named.conf.local
//include "/etc/bind/rndc.key";
include "/etc/bind/named.conf.options";
include "/etc/bind/named.conf.local";
include "/etc/bind/named.conf.default-zones";
2. named.conf.options:
Code:
options {
directory "/var/cache/bind";
allow-transfer {
127.0.0.1;
172.20.100.0/24;
};
allow-query {
127.0.0.1;
172.20.100.0/24;
};
forwarders {
8.8.8.8;
172.20.100.1;
};
auth-nxdomain no; # conform to RFC1035
listen-on { any; };
listen-on-v6 { any; };
};
3. named.conf.local
Code:
ogging {
channel query.log {
file "/var/log/query.log";
severity debug 3;
};
category queries { query.log; };
};
// Consider adding the 1918 zones here, if they are not used in your
// organization
//include "/etc/bind/zones.rfc1918";
zone "middle-earth.local" {
type master;
file "/etc/bind/db.middle-earth.local";
allow-transfer { 127.0.0.1; 172.20.100.0/24; };
allow-update { key "rndc-key" };
notify yes;
};
zone "100.20.172.in-addr.arpa" {
type master;
file "/etc/bind/db.172.20.100";
allow-transfer { 127.0.0.1; 172.20.100.0/24; };
allow-update { key "rndc-key" };
notify yes;
};
4. named.conf.default-zones
Code:
// prime the server with knowledge of the root servers
zone "." {
type hint;
file "/etc/bind/db.root";
};
// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912
zone "localhost" {
type master;
file "/etc/bind/db.local";
};
zone "127.in-addr.arpa" {
type master;
file "/etc/bind/db.127";
};
zone "0.in-addr.arpa" {
type master;
file "/etc/bind/db.0";
};
zone "255.in-addr.arpa" {
type master;
file "/etc/bind/db.255";
};
5. rndc.key
Code:
key "rndc-key" {
algorithm hmac-md5;
secret "xCDX/U9Xr/JZbuFfwyhv9Q==";
};
Using the configuration described above I get the message during start bind:
Code:
rndc: connect failed: 127.0.0.1#953: connection refused
[ OK ]
* Starting domain name service... bind9 [ fail]
and in syslog the same message:
Code:
Nov 15 08:57:12 Arwen named[1388]: loading configuration from '/etc/bind/named.conf'
Nov 15 08:57:12 Arwen named[1388]: none:0: open: /etc/bind/named.conf: permission denied
Nov 15 08:57:12 Arwen named[1388]: loading configuration: permission denied
Nov 15 08:57:12 Arwen named[1388]: exiting (due to fatal error)
So I'm absolutely not an expert, but where could be here the error, is there a different conf file for rndc?
I also tried to use rndc.conf in /etc/bind but the following message is displayed:
Code:
WARNING: key file (/etc/bind/rndc.key) exists, but using default configuration file (/etc/bind/rndc.conf)
rndc: connect failed: 127.0.0.1#953: connection refused
I'm now out of any idea in how could I solve the problem.
Bookmarks