root-servers.net's nameservers change
Informational Message: On 8 August, 2000, Network Solutions took actions in compliance with the cooperative agreement with the Department of Commerce to discontinue use of the 'InterNIC' name. One specific aspect of this change involves the server named rs0.internic.net, which had been the primary name server for the root-servers.net domain name along with secondary servers ns.ripe.net, ns.isi.edu and ns-ext.vix.com. All four of these servers were removed from the root-servers.net domain name and replaced with the following servers which were already functioning as root servers: a.root-servers.net f.root-servers.net k.root-servers.net j.root-servers.net At 1730 EDT, the new suite of name servers began acting authoritatively for the root-servers.net domain. The net zone will be updated to reflect the root-servers.net nameserver entries in serial #2000080801. The four hosts rs0.internic.net, ns.isi.edu, ns.ripe.net, and ns-ext.vix.com will continue to serve the root-servers.net zone with the new list of name servers. These hosts will continue to remain active until the time of the new name server suite exceeds the Time To Live (TTL), as defined in the root-servers.net zone. That TTL is currently set to 3,600,000 seconds, or about 42 days. This is an operational change that transferred very smoothly. You will NOT need to make any configuration changes on your machines. You will NOT need a new root.cache file. -------------------------------------- Brad Verd gTLD Operations Manager Network Solutions Registry Email - bverd@netsol.com ---------------------------------------
Perhaps I missed it... I seem to recall someone from NetSol (after the SOA RNAME fiasco a week ago) saying "Hey, you're right, we screwed up, before we push out any change, however minor, we'll tell people when the change is coming and what it will be, so people will be prepared". Now I'm all warm and happy that this "transferred very smoothly", but I didn't see any "beforehand" notification of this change... (unless my mail server ate it, which I'll accept as a possibility, although I didn't see it in the archives either)... Is there a reason for that, especially given the changes of the recent past going wrong? D At 6:09 PM -0400 8/8/00, Verd, Brad wrote:
Informational Message:
On 8 August, 2000, Network Solutions took actions in compliance with the cooperative agreement with the Department of Commerce to discontinue use of the 'InterNIC' name. One specific aspect of this change involves the server named rs0.internic.net, which had been the primary name server for the root-servers.net domain name along with secondary servers ns.ripe.net, ns.isi.edu and ns-ext.vix.com.
All four of these servers were removed from the root-servers.net domain name and replaced with the following servers which were already functioning as root servers:
a.root-servers.net f.root-servers.net k.root-servers.net j.root-servers.net
At 1730 EDT, the new suite of name servers began acting authoritatively for the root-servers.net domain.
The net zone will be updated to reflect the root-servers.net nameserver entries in serial #2000080801.
The four hosts rs0.internic.net, ns.isi.edu, ns.ripe.net, and ns-ext.vix.com will continue to serve the root-servers.net zone with the new list of name servers. These hosts will continue to remain active until the time of the new name server suite exceeds the Time To Live (TTL), as defined in the root-servers.net zone. That TTL is currently set to 3,600,000 seconds, or about 42 days.
This is an operational change that transferred very smoothly. You will NOT need to make any configuration changes on your machines. You will NOT need a new root.cache file.
-------------------------------------- Brad Verd gTLD Operations Manager Network Solutions Registry Email - bverd@netsol.com ---------------------------------------
-----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of Derek J. Balling Sent: Tuesday, August 08, 2000 4:17 PM To: Verd, Brad; 'nanog@merit.edu' Subject: Re: root-servers.net's nameservers change
Perhaps I missed it... I seem to recall someone from NetSol (after the SOA RNAME fiasco a week ago) saying "Hey, you're right, we screwed up, before we push out any change, however minor, we'll tell people when the change is coming and what it will be, so people will be prepared".
Now I'm all warm and happy that this "transferred very smoothly", but I didn't see any "beforehand" notification of this change... (unless my mail server ate it, which I'll accept as a possibility, although I didn't see it in the archives either)... Is there a reason for
Where were you? Domain Policy's been churning on it for a week. that,
especially given the changes of the recent past going wrong?
D
Informational Message:
On 8 August, 2000, Network Solutions took actions in compliance with the cooperative agreement with the Department of Commerce to discontinue use of the 'InterNIC' name. One specific aspect of this change involves the server named rs0.internic.net, which had been the primary name server for the root-servers.net domain name along with secondary servers ns.ripe.net, ns.isi.edu and ns-ext.vix.com.
All four of these servers were removed from the root-servers.net domain name and replaced with the following servers which were already functioning as root servers:
a.root-servers.net f.root-servers.net k.root-servers.net j.root-servers.net
At 1730 EDT, the new suite of name servers began acting authoritatively for the root-servers.net domain.
The net zone will be updated to reflect the root-servers.net nameserver entries in serial #2000080801.
The four hosts rs0.internic.net, ns.isi.edu, ns.ripe.net, and ns-ext.vix.com will continue to serve the root-servers.net zone with the new list of name servers. These hosts will continue to remain active until
At 6:09 PM -0400 8/8/00, Verd, Brad wrote: the time of the
new name server suite exceeds the Time To Live (TTL), as defined in the root-servers.net zone. That TTL is currently set to 3,600,000 seconds, or about 42 days.
This is an operational change that transferred very smoothly. You will NOT need to make any configuration changes on your machines. You will NOT need a new root.cache file.
-------------------------------------- Brad Verd gTLD Operations Manager Network Solutions Registry Email - bverd@netsol.com ---------------------------------------
participants (3)
-
Derek J. Balling -
Roeland M.J. Meyer -
Verd, Brad