From owner-freebsd-stable@FreeBSD.ORG Thu Aug 2 10:57:08 2007 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2BCDB16A417; Thu, 2 Aug 2007 10:57:08 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) Received: from pobox.codelabs.ru (pobox.codelabs.ru [144.206.177.45]) by mx1.freebsd.org (Postfix) with ESMTP id D02C313C45B; Thu, 2 Aug 2007 10:57:07 +0000 (UTC) (envelope-from rea-fbsd@codelabs.ru) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=one; d=codelabs.ru; h=Received:Date:From:To:Cc:Message-ID:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:Sender:X-Spam-Status:Subject; b=NV15DAmeV4WtmJYKjAuprEieQNhayjIFAUGdVVUk2XT9YW+90ztxcgurYMlTOWn3nGjMwj3kP9OceRlPbbufjuZD97B74Nm+ZevghGgNqqmhMKwLaZe9wvkrOey/EfV5LFs/FfZxsCrmHg4B4pqTR/Ov0N87eQQ/e2Q4Ff4foGU=; Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25]) by pobox.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256) id 1IGYBU-000Kkt-E7; Thu, 02 Aug 2007 14:45:36 +0400 Date: Thu, 2 Aug 2007 14:45:31 +0400 From: Eygene Ryabinkin To: Doug Barton Message-ID: <20070802104531.GJ72909@void.codelabs.ru> References: <200708020114.l721EMvl095981@drugs.dv.isc.org> <200708020135.l721Zm2s026224@apollo.backplane.com> <46B1AE8E.8030307@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <46B1AE8E.8030307@FreeBSD.org> Sender: rea-fbsd@codelabs.ru X-Spam-Status: No, score=-2.3 required=4.0 tests=ALL_TRUSTED,AWL,BAYES_05 Cc: FreeBSD Current , FreeBSD Stable Subject: Re: default dns config change causing major poolpah X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Aug 2007 10:57:08 -0000 Doug, good day. Thu, Aug 02, 2007 at 03:14:38AM -0700, Doug Barton wrote: > Matthew Dillon wrote: > > It has always seemed to me that actually > > downloading a physical root zone file once a week is the most reliable > > solution. > > This is a really bad idea. The root zone changes slowly, but it often > changes more than once a week. Add to that the more-rapid deployment > of new TLDs nowadays and the occasional complete reprovisioning of an > existing TLD, and one week is too long to go between updates. But if one will pull the root zone via FTP/HTTP at the zone's refresh rate or so -- will it be still a bad idea, compared to the AXFR method? -- Eygene