From owner-freebsd-current@FreeBSD.ORG  Sat Oct  9 15:06:15 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id BC3B316A4CE
	for <current@freebsd.org>; Sat,  9 Oct 2004 15:06:15 +0000 (GMT)
Received: from arizona.xtaz.net (kai.xtaz.net [82.68.183.49])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6F70143D53
	for <current@freebsd.org>; Sat,  9 Oct 2004 15:06:15 +0000 (GMT)
	(envelope-from matt@xtaz.net)
Received: from [192.168.1.4] (colorado.xtaz.net [192.168.1.4])
	by arizona.xtaz.net (Postfix) with ESMTP id 45C7D8FC4F;
	Sat,  9 Oct 2004 16:06:14 +0100 (BST)
Message-ID: <4167FE66.7080001@xtaz.net>
Date: Sat, 09 Oct 2004 16:06:14 +0100
From: Matt <matt@xtaz.net>
User-Agent: Mozilla Thunderbird 0.7.3 (X11/20040928)
X-Accept-Language: en-us, en
MIME-Version: 1.0
References: <52639.192.168.1.4.1097321701.squirrel@webmail.xtaz.net>
	<20041009144954.GA887@CARTIER.ro-inc> <4167FD01.3040305@xtaz.net>
In-Reply-To: <4167FD01.3040305@xtaz.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: current@freebsd.org
Subject: Re: rndc/bind9 weirdness
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Oct 2004 15:06:15 -0000

Matt wrote:
> Clive Lin wrote:
> 
>> On Sat, Oct 09, 2004 at 12:35:01PM +0100, Matt Smith wrote:
>>
>>> Basically you can only reload it once and then it'll refuse to talk 
>>> unless
>>> you run /etc/rc.d/named restart.
>>
>>
>>
>> Hi,
>>
>>     My first guess is to verify the /etc/namedb ->
>> /var/named/etc/namedb link. I have production name server running with
>> 5.3-BETA7 in jail without problem, and I can `rndc reload` as many
>> times as I want. (some more jail specific tweaks, although still in
>> default chroot mode.)
>>
>>     If my memory serves me right, I solved the same problem by make
>> the link correct.
>>
>> Cheers
>>
> 
> The symlink and /var/named structure is fine as i completely rm -rf'd 
> them before letting the new named rc.d script create them. I found the 
> issue but am not sure what to do about it. On the second reload there is 
> a message in syslog saying:
> 
> none:0: open: /etc/namedb/rndc.key: permission denied
> 
> So I am assuming because the chroot is set to /var/named it can't access 
> this or something?
> 

Ahh my fault. I found out what it was. In my named.conf I had this from 
when I used to run bind9 from ports with a rndc.conf instead of an rncd.key:

controls {
       inet 127.0.0.1 port 953
       allow { 127.0.0.1; };
};

Commenting this out has made me able to reload it all the time. Sorry 
for the noise people!

Cheers ;-)

Matt.