[158924] in North American Network Operators' Group
=?windows-1252?Q?Re=3A_Advisory_=97_D-root_is_changing_its_IPv4_?=
daemon@ATHENA.MIT.EDU (David Conrad)
Sat Dec 15 18:07:35 2012
From: David Conrad <drc@virtualized.org>
In-Reply-To: <20121215223225.8805A2D13E64@drugs.dv.isc.org>
Date: Sat, 15 Dec 2012 15:07:18 -0800
To: Mark Andrews <marka@isc.org>
Cc: "nanog@nanog.org Group" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Dec 15, 2012, at 2:32 PM, Mark Andrews <marka@isc.org> wrote:
> 3 weeks is not a lot of time to inform every recursive service
> operator in the world that there is a change coming. =20
Given the impact of the change, I figure 3 weeks is plenty.
> Remember nameservers will start logging warning messages as of January =
3rd.
And if they do, recursive service operators who haven't seen the message =
will (if they care) update their root hints. This seems to be exactly =
the right thing. I fail to see the concern here. =20
> There is a big difference between 'This is just fallout from D
> changing it's address' to 'What does this message mean and do I have
> to worry?'
Are BIND's warning messages so opaque that someone who is looking at =
name server log messages can't figure out that the warning is talking =
about a root server IP address being changed?
The handwringing over this issue is a bit over the top.
Regards,
-drc
