hi,

i managed to fix the problem. No worries. In case someone has the same problem feel free to PM me. would be happy to help

Still having problems after making sure your rndc and named keys match? Here is what I did to solve the problem on my server.

1) Create /etc/rndc.key (use a key generator listed in the other posts to get your secret key)

key "rndckey" {
algorithm hmac-md5 ;
secret "MySecretKey";
};

2) Create /etc/rndc.conf (note the include of rndc.key, this ensures the named and rndc apps both have identical keys)

# Start of rndc.conf
options {
default-server localhost;
default-key "rndckey";
};

server localhost {
key "rndckey";
};

include "/etc/rndc.key";

3) Edit /etc/named.conf and change or add these sections:

options {
directory "/etc/named";
pid-file "/var/run/named.pid";
};

zone "localhost" {
allow-update { none; }; type master; file "localhost.zone"; };

.... blah,blah,blah.... more zones here....

include "/etc/rndc.key";

controls {
inet * allow { any; } keys { rndckey; };
};


4) Create /etc/named/localhost.zone

$TTL 86400
@ IN SOA @ root (
43 ; serial
10800 ; refresh
900 ; retry
604800 ; expire
86400 ; ttl
)



IN NS @
IN A 127.0.0.1
IN AAAA ::1


The winning combo was to use the include in both named.conf and rndc.conf so they key matches - AND - make sure a localhost zone file exists on the system. For some reason Bind9 was having issue with a hard-coded 127.0.0.1 in these files.


HTH,
Lance
Sr. Computer Geek
CharlestonSW.com

Hi,

I was trying to configure multiple zones on my DNS on RHEL3 Box. The first zone went fine. The named service was stopped at that time. I started that service and then everything went fine. then i created another zone. But i did not stop the service while editing the /etc/named.conf file and then the zone and reverse files. Now it is giving me the error

rndc: connect failed: connection refused

everytime i try to stop the named service. I also tried various rndc commands but i get the same error message.

I tried removing DNS and then re installing it. I still get the same error. Can somebody help?

Still having problems after making sure your rndc and named keys match? Here is what I did to solve the problem on my server.

1) Create /etc/rndc.key (use a key generator listed in the other posts to get your secret key)

key "rndckey" {
algorithm hmac-md5 ;
secret "MySecretKey";
};

2) Create /etc/rndc.conf (note the include of rndc.key, this ensures the named and rndc apps both have identical keys)

# Start of rndc.conf
options {
default-server localhost;
default-key "rndckey";
};

server localhost {
key "rndckey";
};

include "/etc/rndc.key";

3) Edit /etc/named.conf and change or add these sections:

options {
directory "/etc/named";
pid-file "/var/run/named.pid";
};

zone "localhost" {
allow-update { none; }; type master; file "localhost.zone"; };

.... blah,blah,blah.... more zones here....

include "/etc/rndc.key";

controls {
inet * allow { any; } keys { rndckey; };
};


4) Create /etc/named/localhost.zone

$TTL 86400
@ IN SOA @ root (
43 ; serial
10800 ; refresh
900 ; retry
604800 ; expire
86400 ; ttl
)



IN NS @
IN A 127.0.0.1
IN AAAA ::1


The winning combo was to use the include in both named.conf and rndc.conf so they key matches - AND - make sure a localhost zone file exists on the system. For some reason Bind9 was having issue with a hard-coded 127.0.0.1 in these files.


HTH,
Lance
Sr. Computer Geek
CharlestonSW.com

hi people......finally the rndc bug is out of the stadium......i have found the solution ......
it depends on only the permissions of files and directories...
rndc .conf ........root.named....755
named.conf.......named.named.....755
also if there is errror like ....permission denied on named.pid after running ....named -g -p 53.....then u have to change permissions....of /var/run/named derectory......where the pid resides.....