Ok, good Idea,
This is how looks now my named.conf.local file:
Code:
//logging {
// 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";
//include "/etc/bind/rndc.key";
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-transfer {"none";};
//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 {"none";}; //{ 127.0.0.1; 172.20.100.0/24; };
//allow-update { key "rndc-key" };
notify yes;
};
unfortunately the error is the same, permission denied and connection refused on rndc.
Isn't there any command to disable rndc or unlink it from bind?
Actually there aren't any references to rndc in the named config files....
Should I try to reinstall compleetly bind9 ? purge bind9 and then reinstall?
Bookmarks