Date: Thu, 21 Oct 2004 17:05:56 +0900 From: JINMEI Tatuya / =?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?= <jinmei@isl.rdc.toshiba.co.jp> To: jesk@killall.org Cc: freebsd-current@freebsd.org Subject: Re: Bind 9 bug? (rndc reload) Message-ID: <y7vbrewo5qz.wl@ocean.jinmei.org> In-Reply-To: <09325CBD4E9A0BFBED806921@jesk.int.de.clara.net> References: <200410201610.08983.michael.riexinger@de.clara.net> <09325CBD4E9A0BFBED806921@jesk.int.de.clara.net>
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> On Thu, 21 Oct 2004 10:01:18 +0200, >>>>> jesk <jesk@killall.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?y7vbrewo5qz.wl>