From owner-freebsd-isp@FreeBSD.ORG Wed Aug 2 18:21:37 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 C74F916A4E0 for ; Wed, 2 Aug 2006 18:21:37 +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 3AA5C43D46 for ; Wed, 2 Aug 2006 18:21:36 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 19254 invoked by uid 399); 2 Aug 2006 18:21:36 -0000 Received: from localhost (HELO ?192.168.0.9?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 2 Aug 2006 18:21:36 -0000 Message-ID: <44D0ED2A.4070204@FreeBSD.org> Date: Wed, 02 Aug 2006 11:21:30 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 To: Edda Hochstrate References: <44CE2043.1040308@netuse.de> <44CE5875.9050509@FreeBSD.org> <44CF3B00.2090106@netuse.de> <20060801124403.GA87804@uk.tiscali.com> <44CF51D6.7060406@netuse.de> In-Reply-To: <44CF51D6.7060406@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, Brian Candler 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: Wed, 02 Aug 2006 18:21:37 -0000 Edda Hochstrate wrote: > 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. I'm not sure what you mean by this, but Brian was right. The refresh number in the SOA tells slave servers how often to poll the master(s) for updates, servers that query the authoritative servers (resolvers) don't care about that number. Your best bet would be to ask your customer to drop the refresh period to something like 15 minutes, which should be more than adequate. hth, Doug -- This .signature sanitized for your protection