Hi,

Have problem with Bind. When I do:

[root@thorgal sbin]# cd /
[root@thorgal /]# cd /sbin
[root@thorgal sbin]# service named restart
Stopping named: rndc: connect failed: connection refused [FAILED]
Starting named: [ OK ]
[root@thorgal sbin]#

When I do ps -aux, I cannot see that the named process has started. I also see in the /var/log/messages the following:


Apr 18 15:55:55 thorgal named[10068]: starting BIND 9.2.3 -u named
Apr 18 15:55:55 thorgal named[10068]: using 1 CPU
Apr 18 15:55:55 thorgal named[10068]: loading configuration from '/etc/named.conf'
Apr 18 15:55:55 thorgal named[10068]: no IPv6 interfaces found
Apr 18 15:55:55 thorgal named[10068]: listening on IPv4 interface lo, 127.0.0.1#53
Apr 18 15:55:55 thorgal named[10068]: listening on IPv4 interface eth1, 10.0.0.13#53
Apr 18 15:55:55 thorgal named[10068]: command channel listening on 127.0.0.1#953
Apr 18 15:55:55 thorgal named[10068]: couldn't open pid file 'named.pid': Permission denied
Apr 18 15:55:55 thorgal named[10068]: exiting (due to early fatal error)
Apr 18 15:55:55 thorgal named: named startup succeeded


When I do the following, I get the same result:


[root@thorgal /]# /etc/rc.d/init.d/named restart
Stopping named: rndc: connect failed: connection refused [FAILED]
Starting named: [ OK ]
[root@thorgal /]#


Any ideas what is wrong? Can I make the PID file myself. Where do I have to put it? Any suggestions? I googled already a lot...No of the returns fixes my problem.

Below are my files=>

------------------------------------/etc/named.conf-------------------------------------------------------

[root@thorgal etc]# cat named.conf
options {
directory "/var/named";
pid-file "named.pid";
forwarders {
10.0.0.2;
};

/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
query-source port 53;
//forward only;
recursion yes;
//check-names response warn;
//check-names master warn;
};

//
// a caching only nameserver config
//
controls {
inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};
zone "." IN {
type hint;
file "named.ca";
};


include "/etc/rndc.key";

zone "wauters-mannaert.be" {
type master;
file "/var/named/named.hosts";
};

zone "localhost" {
type master;
file "/var/named/localhost.zone";
};

zone "0.0.127.in-addr.arpa" {
type master;
file "/var/named/local.rev";
};

zone "0.0.10.in-addr.arpa" {
type master;
file "/var/named/named.rev";
};


logging {
channel logDNS {
file "/var/log/bind/logDNS.log";
severity info;
print-severity yes;
};
};



------------------------------------/etc/rncd.key------------------------------------------------------------------

[root@thorgal etc]# cat rndc.key
key rndckey {
algorithm hmac-md5;
secret "m35xbeOVUQ1akui5MJm5kpupxy2p7Lw9v3MjhqkYORa8IClXEgBTTmu3rjj0";
};
[root@thorgal etc]#


------------------------------------/etc/rncd.conf------------------------------------------------------------------

[root@thorgal etc]# cat rndc.conf
/*
* Copyright (C) 2000, 2001 Internet Software Consortium.
*
* Permission to use, copy, modify, and distribute this software for any
* purpose with or without fee is hereby granted, provided that the above
* copyright notice and this permission notice appear in all copies.
*
* THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM
* DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL
* INTERNET SOFTWARE CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT,
* INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING
* FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT,
* NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION
* WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
*/

/* $Id: rndc.conf,v 1.7 2001/01/09 21:40:45 bwelling Exp $ */

/*
* Sample rndc configuration file.
*/

options {
default-server localhost;
default-key "rndckey";
};

server localhost {
key "rndckey";
};

include "/etc/rndc.key";
[root@thorgal etc]#

Looks like user 'named' doesn't have permission to create named.pid in /var/named.

yes u can. use the command touch

# touch named.pid
put it in /var/run where the other pid files are
but i think thats not ur problem try this:
go to /usr/sbin and run
./named-checkconf
this checks ur named.conf file for errors
it might be the rndc key

I've found if you use `service named restart` it doesnt work properly... I've always had to `killall -9 named` then `service named start`

If it's a service, it will not show up in ps aux, but if you do a netstat -anp as root it will tell you the process thats running on the specific port, bind for example and you can check to see if it's running. Bind runs on port 53 fyi

ucould try pgrep -l named I think thats right, should give you process id