From owner-freebsd-isp@FreeBSD.ORG Mon Jul 31 15:23:13 2006 Return-Path: X-Original-To: freebsd-isp@freebsd.org Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 308BA16A4DE for ; Mon, 31 Jul 2006 15:23:13 +0000 (UTC) (envelope-from eh@netuse.de) Received: from mail0.netuse.de (mailout0.netuse.de [195.244.244.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7E4DF43D45 for ; Mon, 31 Jul 2006 15:23:12 +0000 (GMT) (envelope-from eh@netuse.de) Received: from netuse.de (boss [192.168.254.12]) by mail0.netuse.de (8.12.11/8.12.10) with ESMTP id k6VFN9ri007490 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK) for ; Mon, 31 Jul 2006 17:23:09 +0200 (CEST) Received: from [192.168.254.84] (hasenfuss.intern.netuse.de [192.168.254.84]) by netuse.de (8.12.10/8.12.10) with ESMTP id k6VFN6l9026908 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Mon, 31 Jul 2006 17:23:08 +0200 (MEST) Message-ID: <44CE2043.1040308@netuse.de> Date: Mon, 31 Jul 2006 17:22:43 +0200 From: Edda Hochstrate User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-isp@freebsd.org X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AntiVirus: checked by AntiVir Milter 1.0.6; AVE 7.1.1.0; VDF 6.35.1.26 X-AntiVirus: checked by AntiVir Milter 1.0.6; AVE 7.1.1.0; VDF 6.35.1.26 X-Greylist: Sender IP whitelisted,not delayed by milter-greylist-2.0 (mail0.netuse.de [195.244.244.5]); Mon, 31 Jul 2006 17:23:10 +0200 (CEST) Subject: Bind9: rndc reload doesn't work for slave servers X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jul 2006 15:23:13 -0000 Hi, I've a problem with rndc on a bind9 slave server. In my opinion afer an "rndc reload" a slave should query the master for the soa records of all zones stated in named.conf. This is what the slave does when started without any zone files on disk. If the slave has already loaded the zones from the master "rndc reload" has no effect as I can see in tcpdump output, same with "rndc reconfig". "rndc reload 123.org" works as expected. The slave queries the master for the soa record of 123.org and updates the zone if his own serial is older. Is there a way to force a complete reload of a bind9 slave server. Thanks very much, Edda