From owner-freebsd-current@FreeBSD.ORG  Sat Oct  9 11:35:05 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 ABF8C16A4CE
	for <current@freebsd.org>; Sat,  9 Oct 2004 11:35:05 +0000 (GMT)
Received: from kai.xtaz.net (kai.xtaz.net [82.68.183.49])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3D1B243D39
	for <current@freebsd.org>; Sat,  9 Oct 2004 11:35:03 +0000 (GMT)
	(envelope-from matt@xtaz.net)
Received: from webmail.xtaz.net (localhost [127.0.0.1])
	by kai.xtaz.net (Postfix) with ESMTP id 79A138FC4A
	for <current@freebsd.org>; Sat,  9 Oct 2004 12:35:01 +0100 (BST)
Received: from 192.168.1.4
        (SquirrelMail authenticated user matt);
        by webmail.xtaz.net with HTTP;
        Sat, 9 Oct 2004 12:35:01 +0100 (BST)
Message-ID: <52639.192.168.1.4.1097321701.squirrel@webmail.xtaz.net>
Date: Sat, 9 Oct 2004 12:35:01 +0100 (BST)
From: "Matt Smith" <matt@xtaz.net>
To: current@freebsd.org
User-Agent: SquirrelMail/1.5.1 [CVS]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
Subject: 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 11:35:05 -0000

Anyone else seen an issue like this with the new bind9:

root@kai[~]# rndc reload
server reload successful
root@kai[~]# rndc reload
rndc: connection to remote host closed
This may indicate that the remote server is using an older version of
the command protocol, this host is not authorized to connect,
or the key is invalid.

Basically you can only reload it once and then it'll refuse to talk unless
you run /etc/rc.d/named restart.

I am using RELENG_5 and the only bind related things I have in rc.conf are
named_enable="YES" and so it's using the default chroot setup.

I'm guessing the chroot is what's screwing with it but is this expected
behavior?