From owner-freebsd-bugs@FreeBSD.ORG Tue Mar 16 22:30:20 2004 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 18E6E16A4CE for ; Tue, 16 Mar 2004 22:30:20 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06EA743D2F for ; Tue, 16 Mar 2004 22:30:18 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i2H6UHbv033402 for ; Tue, 16 Mar 2004 22:30:17 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.10/8.12.10/Submit) id i2H6UH9A033400; Tue, 16 Mar 2004 22:30:17 -0800 (PST) (envelope-from gnats) Date: Tue, 16 Mar 2004 22:30:17 -0800 (PST) Message-Id: <200403170630.i2H6UH9A033400@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Daniel Rudy Subject: Re: bin/64360: BIND UPDATE: named.root hints file updated X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Daniel Rudy List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Mar 2004 06:30:20 -0000 The following reply was made to PR bin/64360; it has been noted by GNATS. From: Daniel Rudy To: Xin LI Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: bin/64360: BIND UPDATE: named.root hints file updated Date: Tue, 16 Mar 2004 22:25:41 -0800 And somewhere around the time of 03/16/2004 19:32, the world stopped and listened as Xin LI contributed the following to humanity: > On Tue, Mar 16, 2004 at 07:07:42PM -0800, Daniel Rudy wrote: > >>>Description: >> >>/etc/namedb/named.root hints file updated. > > > http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/namedb/named.root > > The update has been done in January. If you are tracking RELENG_4_9, > you may need to manually update it as this is not a security update, > as the change does not fit the security branch criteria. > > Another solution is to manually update your local named.root copy > to the latest cvs version. Considering that the configuration files > are not being changed so often in a security branch, you can safely > do this because you do not need to do mergemaster before next release. > > Cheers, I see. I was not aware of this. I've already downloaded the file from the internic ftp server. Thanks. -- Daniel Rudy