On 2012-12-18, at 11:15, David Conrad d...@virtualized.org wrote:
WRT the root _hints_ change, setting up a cron job to pull, verify, and
install the root hints file periodically (once a month should probably be
sufficient) would probably be a good idea.
This change appears to have been
On Jan 3, 2013, at 11:38 AM, Joe Abley wrote:
On 2012-12-18, at 11:15, David Conrad d...@virtualized.org wrote:
WRT the root _hints_ change, setting up a cron job to pull, verify, and
install the root hints file periodically (once a month should probably be
sufficient) would probably be a
Hi Henry,
On 2013-01-03, at 13:29, Henry Steuart hsteu...@alliedtelecom.net wrote:
Perhaps someone at internic.net could explain why the file in the first
directory is WRONG but that in the second includes the correct info?
[legacy cron jobs pointing at FTP. will obviously not succeed]
;
For anyone who is worried that the root server change might impact them,
they can go to http://www.iana.org/domains/root/files and download the root
zone file. It probably won't need to be updated again until the next round
of gTLDs is approved.
On Dec 17, 2012, at 11:30 PM, ITechGeek i...@itechgeek.com wrote:
For anyone who is worried that the root server change might impact them,
they can go to http://www.iana.org/domains/root/files and download the root
zone file. It probably won't need to be updated again until the next round
of
Actually, I have an excellent memory also. The one thing I do NOT
remember is this much Sturm und Drang over any of the past changes.
increase in number of people who can't resist telling others what they
should do
randy
and ones who don't read posts before responding.
On Mon, Dec 17, 2012 at 8:14 AM, Randy Bush ra...@psg.com wrote:
Actually, I have an excellent memory also. The one thing I do NOT
remember is this much Sturm und Drang over any of the past changes.
increase in number of people who can't
Concomittant wirh reduced risk assessment capability?
Sent from Samsung Mobile
Original message
From: Randy Bush ra...@psg.com
Date:
To: Lynda shr...@deaddrop.org
Cc: North American Network Operators' Group nanog@nanog.org
Subject: Re: Advisory — D-root is changing its
On 16/12/2012 02:26, David Conrad wrote:
The UMD folks are making a change to _their_ infrastructure.
as is their prerogative. It's just that they happen to operate a
particular chunk of Internet infrastructure which is pretty important in
the scale of things.
They have
sent out a notice in
Nick Hilliard wrote:
On 16/12/2012 02:26, David Conrad wrote:
The UMD folks are making a change to _their_ infrastructure.
A site who hosts a Global Internet critical infrastructure is not bound to
the same procedures as a regular site. It takes a certain amount of trust
to have one of the
On 12-12-16 07:07, Nick Hilliard wrote:
No-one's dictating: I'm just asking them politely to take some suggestions
into consideration - suggestions which no-one has so far pointed out as
being unreasonable, and which I would tend to view as being procedurally
sensible and good things to do.
On 12/14/2012 9:50 PM, bmann...@vacation.karoshi.com wrote:
On Fri, Dec 14, 2012 at 08:48:07PM -0800, David Conrad wrote:
On Dec 14, 2012, at 11:02 AM, Joe Ableyjab...@hopcount.ca wrote:
Other root servers have renumbered out of institutional, general-purpose
networks into dedicated networks
On 12/15/2012 02:13 PM, Jared Mauch wrote:
3 weeks is plenty for a service that in 6 months you may see degraded to 12/13
capacity
... or 21/22 capacity, if you have IPv6. :) And the v6 address of D is
not changing.
FWIW I agree with the tempest in a teapot assessment. I think UMD has
Hi,
Additionally, we will be actively monitoring usage after the 6 month
period to determine when best to terminate the service on the old IP.
Good to hear that.
The old address, which is in the middle of UMD's network, is going to be
black-holed once the change is over. Nothing will be on
On 15/12/12 06:03, Jean-Francois Mezei wrote:
There are also a number of much older systems which no longer get
software updates (such as VAX-VMS) so it is good practice to manually
maintain the root.hints files so that over time, you don't accumulate
more than a couple of disused root server
In message 50cb882a.30...@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
On Dec 15, 2012, at 4:58 PM, Mark Andrews ma...@isc.org wrote:
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
On Dec 15, 2012, at 2:13 PM, Jared Mauch ja...@puck.nether.net wrote:
Oh, and you can just download the root zone from
ftp://ftp.internic.net/domain/root.zone ...
Or, perhaps more conveniently, zone transfer the root zone from
xfr.lax.dns.icann.org or
xfr.cjr.dns.icann.org (see
In message 42515678-f2ce-48ce-a0e6-4211c5f0f...@puck.nether.net, Jared Mauch
writes:
On Dec 15, 2012, at 4:58 PM, Mark Andrews ma...@isc.org wrote:
I realise that keeping the old IP functional for some time is =
important
for all the static configurations. But does it matter if a
On 12-12-15 17:32, Mark Andrews wrote:
3 weeks is not a lot of time to inform every recursive service
operator in the world that there is a change coming. Remember
nameservers will start logging warning messages as of January 3rd.
Nameservers will NOT log messages starting Jan 3rd. The old
On Dec 15, 2012, at 2:32 PM, Mark Andrews ma...@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.
Given the impact of the change, I figure 3 weeks is plenty.
Remember nameservers will start logging warning
On 12/15/12 6:07 PM, David Conrad wrote:
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?
What about the people that are running BIND 4 on an old Solaris 2.6
Let us all have a moment of silence to remember all those poor unmanaged
servers out there..Thank you now nuke them all and start over :)
On Sat, Dec 15, 2012 at 6:21 PM, Bryan Fields br...@bryanfields.net wrote:
On 12/15/12 6:07 PM, David Conrad wrote:
Are BIND's warning messages so
On 15/12/2012 23:07, David Conrad wrote:
The handwringing over this issue is a bit over the top.
It's a question of what's procedurally sensible. Sensible things would
include longer notice of the impending change to the root zone, more
widespread notice of what's happening and generally not
On 12-12-15 19:45, Nick Hilliard wrote:
widespread notice of what's happening and generally not poking around with
really important bits of the Internet at times which are well known for
having configuration freezes and/or when many people are going to be on
holidays.
You have 6.75 months to
Nick,
On Dec 15, 2012, at 4:45 PM, Nick Hilliard n...@foobar.org wrote:
On 15/12/2012 23:07, David Conrad wrote:
The handwringing over this issue is a bit over the top.
It's a question of what's procedurally sensible. Sensible things would
include longer notice of the impending change to the
On Sun, Dec 16, 2012 at 12:45:32AM +, Nick Hilliard wrote:
On 15/12/2012 23:07, David Conrad wrote:
The handwringing over this issue is a bit over the top.
It's a question of what's procedurally sensible. Sensible things would
include longer notice of the impending change to the root
If your grandmother were running her own recursive DNS resolver, I expect she
would have no difficulty understanding the message.
It is the young-uns that have difficulty comprehending (and using) the English
language.
Sent from Samsung Mobile
Original message
From:
On 13/12/2012 22:54, Jason Castonguay wrote:
Advisory — D-root is changing its IPv4 address on the 3rd of January.
Jason,
You've just given 3 weeks notice for a component change in one of the few
critical part of the Internet's infrastructure, at a time when most
networks have entered a
On Fri, Dec 14, 2012 at 04:42:46PM +, Nick Hilliard wrote:
On 13/12/2012 22:54, Jason Castonguay wrote:
Advisory — 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 few
critical part of the Internet's
Matthew Newton wrote:
On Fri, Dec 14, 2012 at 04:42:46PM +, Nick Hilliard wrote:
On 13/12/2012 22:54, Jason Castonguay wrote:
Advisory — 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 few
critical part of
Mike,
You will need to update your root.hints file on any of your forwarding DNS
servers. Most OS vendors will include an update but its a good idea to
manually check.
On Fri, Dec 14, 2012 at 10:59 AM, Michael Thomas m...@mtcc.com wrote:
Matthew Newton wrote:
On Fri, Dec 14, 2012 at
On Fri, Dec 14, 2012 at 11:59 AM, Michael Thomas m...@mtcc.com wrote:
Matthew Newton wrote:
On Fri, Dec 14, 2012 at 04:42:46PM +, Nick Hilliard wrote:
On 13/12/2012 22:54, Jason Castonguay wrote:
Advisory — D-root is changing its IPv4 address on the 3rd of January.
You've just given 3
If I had to guess, I would guess that renumbering is likely required to get it
into a more portable address assignment from a multi-homing perspective. Look
at the whois information below
If I were hosting a root server or something similar, I would certainly want it
segregated enough that I
On Fri, Dec 14, 2012 at 08:59:19AM -0800, Michael Thomas wrote:
Matthew Newton wrote:
On Fri, Dec 14, 2012 at 04:42:46PM +, Nick Hilliard wrote:
On 13/12/2012 22:54, Jason Castonguay wrote:
Advisory
You've just given 3 weeks notice for a component change in one of the few
critical part
On Dec 14, 2012, at 8:59 AM, Michael Thomas m...@mtcc.com wrote:
Matthew Newton wrote:
So really stupid question, and hopefully it's just me, do I need to do
something
on my servers?
Update the hints file. /var/named/ somewhere in all likelihood.
Second question: I know that renumbering
Hi Michael,
On 2012-12-14, at 11:59, Michael Thomas m...@mtcc.com wrote:
Matthew Newton wrote:
On Fri, Dec 14, 2012 at 04:42:46PM +, Nick Hilliard wrote:
On 13/12/2012 22:54, Jason Castonguay wrote:
Advisory — D-root is changing its IPv4 address on the 3rd of January.
You've just given
On 14/12/2012 16:52, Matthew Newton wrote:
The old address will continue to work for at least six months
after the transition, but will ultimately be retired from
service.
I'm suggesting a lot more notification than 6 months before 128.8.10.90 is
switched off. And corroborative
On 2012-12-14, at 11:42, Nick Hilliard n...@foobar.org wrote:
You've just given 3 weeks notice for a component change in one of the few
critical part of the Internet's infrastructure, at a time when most
networks have entered a configuration freeze (which will usually finish at
the end of
On Fri, Dec 14, 2012 at 12:45:00PM -0500, Joe Abley wrote:
These changes have happened before (other root servers have renumbered). I
have never heard of an operational problem caused by such an exercise, and I
guarantee there are resolvers running happily today with hints files that are
- Original Message -
From: Nick Hilliard n...@foobar.org
It would be really good to have a formal public statement of intent from
UMD about their long term plans for 128.8.10.90 after retirement so that we
don't have a repeat of the L root hijacking debacle in 2008.
Quite so: UMD:
On Fri, Dec 14, 2012 at 04:42:46PM +, Nick Hilliard wrote:
Jason,
You've just given 3 weeks notice for a component change in one of the few
critical part of the Internet's infrastructure, at a time when most
networks have entered a configuration freeze (which will usually finish at
the
On Fri, Dec 14, 2012 at 11:56 AM, Jay Ashworth j...@baylink.com wrote:
Quite so: UMD: Where will the old IP route after the 6 month period is
complete? Somewhere safe?
In point of fact, ISTM that there *is no way* to make this completely safe;
granted that it's a low percentage attack, and
On 2012-12-14, at 13:17, Joe Antkowiak antko...@gmail.com wrote:
On Fri, Dec 14, 2012 at 11:56 AM, Jay Ashworth j...@baylink.com wrote:
Quite so: UMD: Where will the old IP route after the 6 month period is
complete? Somewhere safe?
In point of fact, ISTM that there *is no way* to make
On 12-12-14 12:13, Joe Abley wrote:
In summary, theory (and practice) tells us that:
1. You should update your hints file from time to time, and
2. If you don't, chances are overwhelmingly good that it will make no
difference, and everything will work as normal.
But this is important to
- Original Message -
From: Joe Abley jab...@hopcount.ca
Quite so: UMD: Where will the old IP route after the 6 month period
is complete? Somewhere safe?
As I understand it (but ask UMD!)
- D-Root is currently numbered out of a general-purpose UMD /16 into a
dedicated,
- Original Message -
From: bmann...@vacation.karoshi.com
So, in short, UMD will still own the losing allocation, and be able
to make
relatively sure nothing else is placed at that IP (though of course
they
won't necessarily be able to make sure no one hijacks that entire
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/14/12 11:42, Nick Hilliard wrote:
On 13/12/2012 22:54, Jason Castonguay wrote:
Advisory — D-root is changing its IPv4 address on the 3rd of
January.
Jason,
You've just given 3 weeks notice for a component change in one of
the few
On Fri, Dec 14, 2012 at 02:46:49PM -0500, Jay Ashworth wrote:
- Original Message -
From: bmann...@vacation.karoshi.com
So, in short, UMD will still own the losing allocation, and be able
to make
relatively sure nothing else is placed at that IP (though of course
they
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
Hi Jean,
On Dec 14, 2012, at 9:12 PM, Jean-Francois Mezei jfmezei_na...@vaxination.ca
wrote:
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
On 12/14/2012 03:12 PM, Jean-Francois Mezei wrote:
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
On Fri, Dec 14, 2012 at 2:13 PM, Jason Castonguay casto...@umd.edu wrote:
The old address, which is in the middle of UMD's network, is going to be
black-holed once the change is over. Nothing will be on that IP once we
move the root off. The rest of UMD's network is staying put. This move
On Fri, Dec 14, 2012 at 03:10:44PM -0600, Joe Antkowiak wrote:
On Fri, Dec 14, 2012 at 2:13 PM, Jason Castonguay casto...@umd.edu wrote:
The old address, which is in the middle of UMD's network, is going to be
black-holed once the change is over. Nothing will be on that IP once we
move
On Fri, Dec 14, 2012 at 3:25 PM, bmann...@vacation.karoshi.com wrote:
because you would not accept a /30 cutout of the UMD /16 coming
from some random IX in Singapore. (see Joe Ableys post earlier
today
on why legacy nodes are / have renumbered.)
/bill
Agreed on
On Dec 14, 2012, at 11:02 AM, Joe Abley jab...@hopcount.ca wrote:
Other root servers have renumbered out of institutional, general-purpose
networks into dedicated networks in the past. I think the last one was B-Root
in 2004,
Actually, it was L in 2007... :)
Regards,
-drc
On Fri, Dec 14, 2012 at 08:48:07PM -0800, David Conrad wrote:
On Dec 14, 2012, at 11:02 AM, Joe Abley jab...@hopcount.ca wrote:
Other root servers have renumbered out of institutional, general-purpose
networks into dedicated networks in the past. I think the last one was
B-Root in 2004,
57 matches
Mail list logo
