From owner-freebsd-isp@FreeBSD.ORG Tue Aug 1 13:06:58 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 D571616A4E0; Tue, 1 Aug 2006 13:06:58 +0000 (UTC) (envelope-from eh@netuse.de) Received: from mail0.netuse.de (mailout0.netuse.de [195.244.244.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1DE0B43D45; Tue, 1 Aug 2006 13:06:57 +0000 (GMT) (envelope-from eh@netuse.de) Received: from netuse.de (boss [192.168.254.12]) by mail0.netuse.de (8.12.11/8.12.10) with ESMTP id k71D6tdB027539 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=OK); Tue, 1 Aug 2006 15:06:55 +0200 (CEST) Received: from [192.168.254.84] (hasenfuss.intern.netuse.de [192.168.254.84]) by netuse.de (8.12.10/8.12.10) with ESMTP id k71D6sl9000743 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 1 Aug 2006 15:06:54 +0200 (MEST) Message-ID: <44CF51D6.7060406@netuse.de> Date: Tue, 01 Aug 2006 15:06:30 +0200 From: Edda Hochstrate User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brian Candler References: <44CE2043.1040308@netuse.de> <44CE5875.9050509@FreeBSD.org> <44CF3B00.2090106@netuse.de> <20060801124403.GA87804@uk.tiscali.com> In-Reply-To: <20060801124403.GA87804@uk.tiscali.com> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AntiVirus: checked by AntiVir Milter 1.0.6; AVE 7.1.1.0; VDF 6.35.1.32 X-AntiVirus: checked by AntiVir Milter 1.0.6; AVE 7.1.1.0; VDF 6.35.1.32 X-Greylist: Sender IP whitelisted,not delayed by milter-greylist-2.0 (mail0.netuse.de [195.244.244.5]); Tue, 01 Aug 2006 15:06:55 +0200 (CEST) Cc: freebsd-isp@freebsd.org, Doug Barton Subject: Re: Re: 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: Tue, 01 Aug 2006 13:06:58 -0000 Brian Candler wrote: > If you are going to do a 'kill -HUP' every 5 minutes, say, then you are > generating a lot of work for your own server and every customer's master > server. Once an hour. Then it takes 10 min. apx. for 3000 zones. > > If you have a particular customer who has made a change and explicitly asks > you to refresh their zone, then you can 'rndc reload ' as said before. Yes. But not, if your customer himself has 900 zones and wants your slaves to be as up-to-date as his primary. But maybe we will script it with 'rndc reload ', right. > > However, note that your slave server will poll each of the masters at the > refresh interval in their SOA record anyway. So if a particular customer > wants you to poll their zone more frequently, then they can just reduce the > refresh time in their SOA record, and your server will honour their request. > That gives you the best of all worlds - frequent polling for those customers > who want or need it, and occasional polling for everyone else. In our opinion as an ISP the refresh time is for the world of resolvers. Authoritative nameservers (especially slaves serving hidden primaries) should be as close as possible to the primary. Best regards, Edda