[158919] in North American Network Operators' Group
Re: Advisory =?windows-1252?Q?=97_D-root_is_changing_its?=
daemon@ATHENA.MIT.EDU (Mark Andrews)
Sat Dec 15 16:59:20 2012
To: Jean-Francois Mezei <jfmezei_nanog@vaxination.ca>
From: Mark Andrews <marka@isc.org>
In-reply-to: Your message of "Fri, 14 Dec 2012 15:12:26 CDT."
<50CB882A.30502@vaxination.ca>
Date: Sun, 16 Dec 2012 08:58:46 +1100
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
In message <50CB882A.30502@vaxination.ca>, Jean-Francois Mezei writes:
> On 12-12-14 15:13, Jason Castonguay wrote:
>
> > I've given 3 weeks + 6 months (at least) notice on a service change that
> > will not be noticed by most anyone.
>
> Upon hearing your announcement, I went and dig myself a new root.hints
> file from one of the root servers. the "D" root is still pointing to the
> old address. So I had to go in and manually edit the root.hints file
> myself. I blame you for all that extra work :-)
Yet you appear to have not read the announcement. :-)
> Would there be any impact to having the root servers immediatly provide
> the new IP for the D server so that a
> dig ns . @a.root-servers.net. > root.hints would yield the new updated
> file ?
Then people would complain "You didn't give us any warning". This is a
HEADSUP of an upcoming change.
> I realise that keeping the old IP functional for some time is important
> for all the static configurations. But does it matter if a dynamic list
> is updated "real time" without much advance warning ?
3 weeks is not a lot of "advance warning".
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: marka@isc.org
