[47200] in North American Network Operators' Group
Re: root zone file
daemon@ATHENA.MIT.EDU (Paul Vixie)
Sun Apr 28 11:09:19 2002
To: nanog@merit.edu
Reply-To: namedroppers@ops.ietf.org
From: Paul Vixie <vixie@vix.com>
Date: 28 Apr 2002 08:08:46 -0700
In-Reply-To: <5.1.0.14.2.20020426151556.0287ae60@oak.higgs.net>
Message-ID: <g3k7qrrhc1.fsf@as.vix.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Errors-To: owner-nanog-outgoing@merit.edu
> Replacing the hints file with the top level zone speeds up lookups,
nope. there are less than 300 top level delegations, and a proper
caching implementation will only hit the roots once a week per tld.
> and removes the burden from the root servers:
wrong again. (consider the impact of all those axfr's, from millions
of name servers, whenever the root zone changes.)
but what it _will_ do is add one more config file which contains a
dotted quad that might have to change some day. every few years a
root name server is added or moved. everything is fine as long as
there is _some_ overlap between your hints and the truth. but it's
a whole lot easier to automate the change tracking for a hints file
than for something that tries to make every one of millions of name
servers into stealth slaves of the "." zone.
i've set the reply-to to namedroppers, since this is really not a
north american operations issue.
