From owner-freebsd-isp@FreeBSD.ORG Wed Jul 6 15:02:15 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 DC74916A41C for ; Wed, 6 Jul 2005 15:02:15 +0000 (GMT) (envelope-from john@essenz.com) Received: from beck.quonix.net (beck.quonix.net [146.145.66.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8B3A543D45 for ; Wed, 6 Jul 2005 15:02:15 +0000 (GMT) (envelope-from john@essenz.com) Received: from beck.quonix.net (localhost [127.0.0.1]) by beck.quonix.net (8.13.4/8.13.4) with ESMTP id j66F241d022982 for ; Wed, 6 Jul 2005 11:02:04 -0400 (EDT) Received: from localhost (essenz@localhost) by beck.quonix.net (8.13.4/8.13.4/Submit) with ESMTP id j66F24ef022979 for ; Wed, 6 Jul 2005 11:02:04 -0400 (EDT) X-Authentication-Warning: beck.quonix.net: essenz owned process doing -bs Date: Wed, 6 Jul 2005 11:02:04 -0400 (EDT) From: John Von Essen X-X-Sender: essenz@beck.quonix.net To: freebsd-isp@freebsd.org In-Reply-To: <06ef01c581f6$c54fb3c0$de0a0a0a@visionsix.com> Message-ID: <20050706105612.W22721@beck.quonix.net> References: <3b88b80a0507051933f4750f3@mail.gmail.com> <06ef01c581f6$c54fb3c0$de0a0a0a@visionsix.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SpamAssassin-3.0.3-Score: -2.82/5.8 ALL_TRUSTED X-MimeDefang-2.51: beck.quonix.net X-Scanned-By: MIMEDefang 2.51 on 146.145.66.90 Subject: 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 15:02:16 -0000 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