From owner-freebsd-isp@FreeBSD.ORG Mon Jul 31 19:22:36 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 AA1F816A4DE for ; Mon, 31 Jul 2006 19:22:36 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx24.fluidhosting.com [204.14.89.7]) by mx1.FreeBSD.org (Postfix) with SMTP id 68B0C43D72 for ; Mon, 31 Jul 2006 19:22:34 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 30569 invoked by uid 399); 31 Jul 2006 19:22:33 -0000 Received: from localhost (HELO ?192.168.0.3?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 31 Jul 2006 19:22:33 -0000 Message-ID: <44CE5875.9050509@FreeBSD.org> Date: Mon, 31 Jul 2006 12:22:29 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.5 (X11/20060729) MIME-Version: 1.0 To: Edda Hochstrate References: <44CE2043.1040308@netuse.de> In-Reply-To: <44CE2043.1040308@netuse.de> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-isp@freebsd.org Subject: Re: 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 19:22:36 -0000 Edda Hochstrate wrote: > 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. Well, unfortunately for you the BIND developers do not agree with you. I could argue that there are good reasons not to do what you're suggesting, but I suspect that is not a useful discussion. > This is what the slave does when started without any zone files on disk. If that's the behavior you want, and you don't have a lot of zones to deal with, you could always restart the server instead of using rndc reload. > Is there a way to force a complete reload of a > bind9 slave server. Other than restarting as I suggested above, you could either recursively use rndc reload , or rndc refresh . Now that I've answered your question, I'd like to suggest that you perhaps reconsider this goal? If your master and slave name servers are properly configured, you shouldn't have to do this at all. The master should be sending out notifys for domains when they are updated, which your slaves can then act on in near real time. What conditions are you seeing that lead you to believe that refreshing all your zones at once is necessary? hth, Doug -- This .signature sanitized for your protection