From owner-freebsd-current@FreeBSD.ORG Thu Oct 21 08:06:00 2004 Return-Path: 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 CD59616A4CE for ; Thu, 21 Oct 2004 08:06:00 +0000 (GMT) Received: from shuttle.wide.toshiba.co.jp (shuttle.wide.toshiba.co.jp [202.249.10.124]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4687843D54 for ; Thu, 21 Oct 2004 08:06:00 +0000 (GMT) (envelope-from jinmei@isl.rdc.toshiba.co.jp) Received: from ocean.jinmei.org (shuttle.wide.toshiba.co.jp [3ffe:501:100f::35]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 74AD415210; Thu, 21 Oct 2004 17:05:57 +0900 (JST) Date: Thu, 21 Oct 2004 17:05:56 +0900 Message-ID: From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= To: jesk@killall.org In-Reply-To: <09325CBD4E9A0BFBED806921@jesk.int.de.clara.net> References: <200410201610.08983.michael.riexinger@de.clara.net> <09325CBD4E9A0BFBED806921@jesk.int.de.clara.net> User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI) Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan. MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: Bind 9 bug? (rndc reload) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Oct 2004 08:06:00 -0000 >>>>> On Thu, 21 Oct 2004 10:01:18 +0200, >>>>> jesk said: >> i have Freebsd 5.3 beta with the new bind9 in base, running chrooted. >> I speciefied transfer-source. This works without a problem, but when >> doing a rndc reload, the transfer source seems to be ignored, with rndc >> reconfig it works. Did I made something wrong? > I recognized the same problem. I got two different ip addresses on my bind > machine and when iam doing a reload of a zone or a whole reload then it > will ignore the configured transfer-source address and will use the primary > ip address of the interface. > iam using freebsd 5.3 beta6 with bind9.3.0 chrooted. Just for checking, is "chrooted" an essential part of the problem? That is, does reloading server work fine if named is not chrooted? JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. jinmei@isl.rdc.toshiba.co.jp