From owner-freebsd-isp@FreeBSD.ORG Thu Jul 7 17:02:19 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 67BE816A41C for ; Thu, 7 Jul 2005 17:02:19 +0000 (GMT) (envelope-from admin@newcub.kcnet.org) Received: from mx3.kcnet.org (mx3.kcnet.org [64.8.76.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id ECE2043D45 for ; Thu, 7 Jul 2005 17:02:18 +0000 (GMT) (envelope-from admin@newcub.kcnet.org) Received: from cub.kcnet.org (cub.kcnet.org [64.8.76.18]) by mx3.kcnet.org (8.13.1/8.13.1) with ESMTP id j67G2Jbv009119; Thu, 7 Jul 2005 12:02:19 -0400 (EDT) (envelope-from admin@newcub.kcnet.org) Received: from [127.0.0.1] ([172.20.5.25]) by cub.kcnet.org (8.13.2/8.13.2) with ESMTP id j67H23Nq079354; Thu, 7 Jul 2005 13:02:05 -0400 Message-ID: <42CD600B.5030805@newcub.kcnet.org> Date: Thu, 07 Jul 2005 13:02:03 -0400 From: Newcub Admin User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "freebsd-isp@freebsd.org" References: <20050706183443.0C73843D48@mx1.FreeBSD.org> In-Reply-To: <20050706183443.0C73843D48@mx1.FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.49 on 64.8.76.27 Cc: John Von Essen 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: Thu, 07 Jul 2005 17:02:19 -0000 Simon wrote: >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" >> >> >> > > >_______________________________________________ >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" > > > Have you considered using powerdns www.powerdns.com. It uses MySQL for a backend, so there are no config files to maintain, and you can easily replicate the database to distribute the load. I can't yet testify to its ability to withstand a heavy loads, because I have not put it in production. So far in my testing, it is working flawlessly. Rob Harrington KCnet