[158867] in North American Network Operators' Group
=?windows-1252?Q?Re=3A_Advisory_=97_D=2Droot_is_changing_its_IPv4_address?=
daemon@ATHENA.MIT.EDU (Christopher Morrow)
Fri Dec 14 12:14:47 2012
In-Reply-To: <50CB5AE7.8070709@mtcc.com>
Date: Fri, 14 Dec 2012 12:11:50 -0500
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Michael Thomas <mike@mtcc.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Fri, Dec 14, 2012 at 11:59 AM, Michael Thomas <mike@mtcc.com> wrote:
> Matthew Newton wrote:
>>
>> On Fri, Dec 14, 2012 at 04:42:46PM +0000, Nick Hilliard wrote:
>>>
>>> On 13/12/2012 22:54, Jason Castonguay wrote:
>>>>
>>>> Advisory =97 D-root is changing its IPv4 address on the 3rd of January=
.
>>>
>>> You've just given 3 weeks notice for a component change in one of the f=
ew
>>> critical part of the Internet's infrastructure, at a time when most
>>
>>
>> I think that /was/ the advance notification - you've got 6 months :)
>>
>> "The old address will continue to work for at least six months
>> after the transition, but will ultimately be retired from
>> service."
>
>
> So really stupid question, and hopefully it's just me, do I need to do
> something
> on my servers?
your crontab that updates your root-hints may already have caught the chang=
e...
> Second question: I know that renumbering is important in the abstract, bu=
t
> is there
> really an overwhelming reason why renumbering the root servers is critica=
l?
> Shouldn't
> they all be in PI space for starters?
>
;; ANSWER SECTION:
d.root-servers.net. 604800 IN A 128.8.10.90
128.8.0.0/16 - legacy space...
> Mike
>
