From owner-freebsd-isp@FreeBSD.ORG Wed Jul 6 18:34:44 2005 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 A145F16A41C for ; Wed, 6 Jul 2005 18:34:44 +0000 (GMT) (envelope-from simon@optinet.com) Received: from cobra.acceleratedweb.net (cobra-gw.acceleratedweb.net [207.99.79.37]) by mx1.FreeBSD.org (Postfix) with SMTP id 0C73843D48 for ; Wed, 6 Jul 2005 18:34:43 +0000 (GMT) (envelope-from simon@optinet.com) Received: (qmail 29912 invoked by uid 110); 6 Jul 2005 18:34:42 -0000 Received: from ool-18ba9d5e.dyn.optonline.net (HELO win2kpc1) (simon%optinet.com@24.186.157.94) by cobra.acceleratedweb.net with SMTP; 6 Jul 2005 18:34:42 -0000 From: "Simon" To: "freebsd-isp@freebsd.org" , "John Von Essen" Date: Wed, 06 Jul 2005 14:38:21 -0400 Priority: Normal X-Mailer: PMMail 2000 Professional (2.20.2661) For Windows 2000 (5.0.2195;4) In-Reply-To: <20050706105612.W22721@beck.quonix.net> MIME-Version: 1.0 Message-Id: <20050706183443.0C73843D48@mx1.FreeBSD.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: rndc reload and BIND9 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: Wed, 06 Jul 2005 18:34:44 -0000 Yes, reload is graceful, it will only load named.conf and new zones, it will not touch preloaded zones. Having 2 masters makes no sense, unless you are actually splitting the zone files between them. Unless you perform a cold start of your bind, transfers only occur when a serial number is updated (upon reload) or when a zone expires. -Simon On Wed, 6 Jul 2005 11:02:04 -0400 (EDT), John Von Essen wrote: > >Following a post I had about BIND9, I need to verify a certain behavior >with BIND9 and issuing a rndc reload. > >Instead, of having a master and slave, I am going to have two masters. One >master is the real master, the other gets replicated via rsync. The main >reason for this approach is to cut down on all the zone transfers (we >have 12,000 domains). > >After every hourly rsync, I will issue a rndc reload. If anything has >changed, named will see it with the new serial number. Does the reload >keep dns functionality up and running while it performs the reload? > >A pure stop and start will take about 55 seconds, which isn't acceptable >every hour. But if the reload (which appears to take 10 seconds) is >gracefull and keep existing functionality intact while it reloads, then >that would be great. Just need to verify. > >Thanks >John >_______________________________________________ >freebsd-isp@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-isp >To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org" >