Hi all,

I'm hoping someone can spot the error I have in config here. I've got a RH EL3 server running as a DNS server.

When I run service named start, it seems to start OK.
When I run service named stop, or restart, I get the following error.....

Stopping named: rndc: connect failed: connection refused [FAILED]

I have attached my /etc/rndc.key and .conf files, and also my named.conf file below. I don't know what I have got wrong.

------------------------/etc/rndc.key---------------------------------
key "DHCP_UPDATER" {
algorithm hmac-md5;
secret "HqNEJNJlrx4UHqaMH1AY1Ec0zIdmSatKzBzxyXdHDb202NEN9T8tjLsxLmmS";
};
----------------------------------------------------------------------------

-----------------------/etc/rndc.conf-----------------------------------
options {
default-server localhost;
default-key "DHCP_UPDATER";
};

server localhost {
key "DHCP_UPDATER";
};

include "/etc/rndc.key";
-----------------------------------------------------------------------------

-------------------------/etc/named.conf--------------------------------
options {
directory "/var/named";
};
key DHCP_UPDATER {
algorithm hmac-md5;
secret "HqNEJNJlrx4UHqaMH1AY1Ec0zIdmSatKzBzxyXdHDb202NEN9T8tjLsxLmmS";
};
controls {
inet 127.0.0.1 allow { localhost; } keys { DHCP_UPDATER; };
};
zone "." {
allow-update { DHCP_UPDATER; };
type hint;
file "named.ca";
};
zone "localhost" {
allow-update { DHCP_UPDATER; };
type master;
file "localhost.zone";
};
zone "0.0.127.in-addr.arpa" {
allow-update { DHCP_UPDATER; };
type master;
file "named.local";
};
zone "TSD" {
allow-update { DHCP_UPDATER; };
type master;
file "TSD.zone";
};
zone "192.168.0.in-addr.arpa" {
allow-update { DHCP_UPDATER; };
type master;
file "192.168.0.in-addr.arpa.zone";
};
include "/etc/rndc.key";
---------------------------------------------------------------------------------



If anyone can help me that would be great!!

Thanks alot,

Regards
Craig

-------------------------/etc/named.conf--------------------------------
options {
directory "/var/named";
};
key DHCP_UPDATER {
must be in "DHCP_UPDATER"

and
inet 127.0.0.1 allow { localhost; } keys { DHCP_UPDATER; };
"" forgot ... and below too

in rndc.conf
include "/etc/rndc.key";
move in begin of file

After start named check log and named must listen 953 port
netstat -an|grep 953

Hello yuray,

Thanks for your reply. I have fixed up the " " in the files, thank you for that. I have also moved "/etc/rndc.conf" to the beginning of the file.

I am still getting the problem though. netstat -an|grep 953 doesn't show anything running on that port.

I am sure named is trying to start on port 953 because of the 'controls' section in my named.conf.

If I do a service named start, it looks like it works, it gives me the green [OK]

But when I do a service named stop, or restart, it fails giving the error I stated in my first post here.

Thanks for your help so far.

Regards
Craig

"I am still getting the problem though. netstat -an|grep 953 doesn't show anything running on that port."

Check log files. Usually, named write good log if is something wrong.
While you not see netstat -an|grep 953 green -- rndc is not to be work.

Goodluck.

I think I'm REALLY close now : ) I've done some googling but can't nail it.

In /var/log/messages when I try and start named, I get about 15 lines of what looks good, but then get this.

Dec 15 07:59:28 TSD-Support named[2370]: /etc/named.conf:28: undefined ACL 'DHCP_UPDATER'
Dec 15 07:59:28 TSD-Support named[2370]: loading configuration: not found
Dec 15 07:59:28 TSD-Support named[2370]: exiting (due to fatal error)

This is line 28 of named.conf....
allow-update { "DHCP_UPDATER"; };

If I comment out line 28, I then get the same error on line 34 which is exactly the same line.

I guess I am supposed to define the ACL for allow-update, or DHCP_UPDATER??

The owner and group owner of /etc/named.conf is named

Thanks for all of your help so far : )

Regards
Craig

Hi again,

I got it. named is now starting and stopping with no errors Thanks SO much for your help yuray!!!

I don't know whether to make a new topic or add it on to this. I just tried to test it with a machine by adding it to the new network.

When I do (from an XP machine) nslookup TSD-Support, or any machine name. I get the following.....

DNS request timed out...
timeout was 2 seconds.
*** Can't find server name for address 192.168.0.1: Timed out
*** Default servers are not available
Server: UnKnown
Address: 192.168.0.1

I have my firewall turned off.
I can ping the DNS server (192.168.0.1) with no problems.
A strange thing is, even when I do an nslookup from the server, I get
;; connection timed out; no servers could be reached

Strange??

Thanks heaps.
Craig

Sometimes good ping is not good as looks like.
Check what packets from XP receive on dns server and dns answer XP
Tcpdump on dns server is you friend.

Craig,

I'm in a N.Sydney Datacenter right now and I am literally banging my head against the wall from RHEL 3 AS giving me $h1t about rndc connection refused. Your thread is the ONLY one on the whole WWW that seems to make sense. I am getting the exact smae errors as you. PLEASE advise as to what you did to fix the error.

THanks,
Nick

Hi.

I got it going mate

If you want me to contact you PM me your details. I'll let you know exactly what I did. It all makes sense why I couldn't get it going.

>Craig

This is exactly the information I need.. can anyone post here or PM me the details on how to fix this issue? I would deeply appreciate it. Thanks!

Please post the answer to this, I also am having the exact same problem.

Just curious why you would pm the answer, isnt that the point of the forum, so anyone can find the answer?

solved my problem....

my rndc.key file was empty in my /var/named/chroot/etc/ directory
copied the rndc.key file that was in my /etc directory to /var/named/chroot/etc directory and all is well....

make sure all your files there are correct and atleast have something in them