Named stops responding after reboot?

[aklist_bind at enigmedia.com]

----- Original Message ----- 
From: "James A Griffin" <agriffin at cpcug.org>
To: <aklist_bind at enigmedia.com>
Cc: <bind-users at isc.org>
Sent: Wednesday, June 29, 2005 5:59 PM
Subject: Re: Named stops responding after reboot?


> At a guess your FC2 was configured to run named chrooted.  Try stoping
> it and restarting with:
>
> /etc/rc.d/init.d/named start
>
> If my guess is wrong, then so is my suggestion.

Hmmm...I tried starting it that way, and I got the following syslog 
messages:

Jun 29 19:02:00 default named[2453]: using 1 CPU
Jun 29 19:02:00 default named[2453]: loading configuration from 
'/etc/named.conf'
Jun 29 19:02:00 default named[2453]: listening on IPv4 interface lo, 
127.0.0.1#53
Jun 29 19:02:00 default named[2453]: listening on IPv4 interface eth0, 
192.168.1.200#53
Jun 29 19:02:00 default named[2453]: couldn't add command channel 
127.0.0.1#953: not found
Jun 29 19:02:00 default named[2453]: couldn't add command channel ::1#953: 
not found
Jun 29 19:02:00 default named[2453]: running
Jun 29 19:02:00 default named: named startup succeeded


but it's still not responding to queries

>
> aklist_bind at enigmedia.com wrote:
>>Hi All: I had a relatively new install of Fedora Core2 with BIND 9.2.3
>>running for a few months without incident.
>>
>>I recently had to move the server and powered it off. When I rebooted it,
>>named did not start automatically.
>>
>>I'm at a remote location and am able to SSH into the server. I started 
>>named
>>with:
>>
>>/usr/sbin/named -c /etc/named.conf -u named
>>
>>and there were no errors in the syslog, just:
>>
>>Jun 29 11:38:13 default named[2310]: using 1 CPU
>>Jun 29 11:38:13 default named[2310]: listening on IPv4 interface lo,
>>127.0.0.1#53
>>Jun 29 11:38:13 default named[2310]: listening on IPv4 interface eth0,
>>192.168.1.200#53
>>Jun 29 11:38:13 default named[2310]: command channel listening on
>>127.0.0.1#953
>>
>>which is what I'd expect to see.
>>
>>If I dig @localhost for a local domain I get the correct response.
>>If I dig @192.168.1.200 I also get a correct response.
>>If I dig for a non-local domain I also get a good response.
>>
>>But if I try to connect from anywhere else, I get:
>>
>>"failed, couldn't connect to nameserver"
>>
>>And it's not responding to any queries from any other box, either on the
>>local subnet or outside. It's also not responding to update requests from 
>>a
>>slave outside the subnet.
>>
>>Sorry for the lack of detail...let me know if there's any more info I can
>>provide that will help in diagnosing the problem!
>>
>>TIA, Andrew
>>
>>
>>
>
>