*****PLEASE NOTE*****
This is an important Informational Message to the internet community:
November 5, 2002, the IP address for J.root-servers.net will
change in the authoritative NS set for "dot". The change will
be reflected in zone serial # 2002110501.
This WILL require a change to your root hints file. The new
file will be available via anonymous ftp from rs.internic.net:/domain/named.root as well as ftp.internic.net:/doamin/named.root starting 11/5/02 1700UTC (12pm
EST/9am PST).
Both the new and old j.root-servers.net IP space will provide
answers in parallel for the foreseeable future.
This WILL require a change to your root hints file. The new
[...]
Both the new and old j.root-servers.net IP space will provide
answers in parallel for the foreseeable future.
Since its been 5 years since the hints/cache boot file has changed,
it may be useful to remind people an immediate change to your
local configuration files is not required. You don't need to
slashdot internic.net tomorrow morning trying to download the file.
As long as 1 listed IP address responds with the current list of root
servers, the server doesn't even need to be a root server itself, your
name server should figure out who are the current roots. In the 1980's
and 1990's when the hints/cache file changed regularly, some people when
years without updating it. Or only updated it when they upgraded their
name server code.
Why is it that the PGP keys with which the root zone cache file is
being signed aren't widely available? The files are signed with keyid
C1D27AF9 which I cannot retrieve from, for instance, the MIT PGP
keyserver. Given the importance of the file it would be nice to verify
the data.
"John Crain" <crain@icann.org> writes:
> November 5, 2002, the IP address for J.root-servers.net will
> change in the authoritative NS set for "dot".
Why is this change being made?
My guess would be because of the proximity of a.root-servers.net
(198.41.0.4) and j.root-servers.net (198.41.0.10), which are in the same
/24 announced in BGP.
Why is it that the PGP keys with which the root zone cache file is
being signed aren't widely available? The files are signed with keyid
C1D27AF9 which I cannot retrieve from, for instance, the MIT PGP
keyserver. Given the importance of the file it would be nice to verify
the data.
actually...a more interesting point from the data you posed here is:
(a) the change to j's address noted in the original message had
already been made (they show 2002110500 whereas the change was
supposed to be in 2002110501).
(b) l was a little out of date, and b was as well earlier that day (it
wasn't serving the new address).
