
Dear all, Given the current situation of KPNQwest and the possibility of its services going offline sometime soon, the RIPE NCC in agreement with KPNQwest will be temporally hosting this server (ns.eu.net) in its premises. This is to avoid major problems in the Internet as this server is secondary for a large number of ccTLD's zones, and thousand other zones. We (AS3333) will be soon announcing the 192.16.202.0/24 prefix. Trusting that this is welcome news. Best regards. -- RIPE NCC -- Daniel.Diaz Operations Manager RIPE NCC

Given the current situation of KPNQwest and the possibility of its services going offline sometime soon, the RIPE NCC in agreement with KPNQwest will be temporally hosting this server (ns.eu.net) in its premises.
nice emergency hack and sorry to whine. but i used them both to get diversity. when in less of a panic, please move it to moscow or something. randy

At 11:04 -0700 5/6/02, Randy Bush wrote:
Given the current situation of KPNQwest and the possibility of its services going offline sometime soon, the RIPE NCC in agreement with KPNQwest will be temporally hosting this server (ns.eu.net) in its premises.
nice emergency hack and sorry to whine. but i used them both to get diversity.
Hi Randy, there are 16 ccTLDs for which ns.ripe.net and ns.eu.net are both secondary. So we will definitely request those ccTLDs to look for a new host as soon as possible. The rest can take bit more time to think what they want to do since ns.eu.net will keep running. We are offering secondary service on ns.ripe.net for any ccTLD that we weren't sencodaring for, as are other people. The idea is not to have ns.eu.net running for ever, just to enable people to have time to take rational decisions, without the fear of having the server going away because of some unexpected turn of events.
when in less of a panic, please move it to moscow or something.
Panic? what panic? this is just common sense Joao
randy

On Thu, 6 Jun 2002 01:08:46 +0200 Joao Luis Silva Damas <joao@ripe.net> wrote:
At 11:04 -0700 5/6/02, Randy Bush wrote:
Given the current situation of KPNQwest and the possibility of its services going offline sometime soon, the RIPE NCC in agreement with KPNQwest will be temporally hosting this server (ns.eu.net) in its premises.
nice emergency hack and sorry to whine. but i used them both to get diversity.
Hi Randy,
there are 16 ccTLDs for which ns.ripe.net and ns.eu.net are both secondary. So we will definitely request those ccTLDs to look for a new host as soon as possible.
Hi Randy, hi Joao, dear routing-wg, probably my Company (GATEL, AS13129) is able to host a secondary server for the ccTLDs. The question is rather what are the hardware "requirements" for the secondary server. We have sufficient bandwidth capacity available and rack space as well.
The rest can take bit more time to think what they want to do since ns.eu.net will keep running.
Well done ! Congrats for the good ideas and coordination work.
We are offering secondary service on ns.ripe.net for any ccTLD that we weren't sencodaring for, as are other people.
The idea is not to have ns.eu.net running for ever, just to enable people to have time to take rational decisions, without the fear of having the server going away because of some unexpected turn of events.
when in less of a panic, please move it to moscow or something.
Panic? what panic? this is just common sense
right. it's not panic. --jan -- Jan Ahrent Czmok - Senior Network Engineer - Access Networks Global Access Telecommunications, Inc. - Stephanstr. 3 - 60313 Frankfurt voice: +49 69 299896-35 - fax: +49 69 299896-66 - email: czmok@gatel.de

Hi People, Here from Intelideas (AS12359) we are ready for hosting ccTLDs in our network. We are present in Espanix, Linx, Catnix and diverse upstreams. Our contact data: DNS: dns@intelideas.com DNS Master: Enrique Iglesias Rodriguez. (+34 917882517) regards, Daniel Intelideas On Thursday 06 June 2002 01:08, Joao Luis Silva Damas wrote:
At 11:04 -0700 5/6/02, Randy Bush wrote:
Given the current situation of KPNQwest and the possibility
of its services going offline sometime soon, the RIPE NCC in agreement with KPNQwest will be temporally hosting this server (ns.eu.net) in its premises.
nice emergency hack and sorry to whine. but i used them both to get diversity.
Hi Randy,
there are 16 ccTLDs for which ns.ripe.net and ns.eu.net are both secondary. So we will definitely request those ccTLDs to look for a new host as soon as possible. The rest can take bit more time to think what they want to do since ns.eu.net will keep running.
We are offering secondary service on ns.ripe.net for any ccTLD that we weren't sencodaring for, as are other people.
The idea is not to have ns.eu.net running for ever, just to enable people to have time to take rational decisions, without the fear of having the server going away because of some unexpected turn of events.
when in less of a panic, please move it to moscow or something.
Panic? what panic? this is just common sense
Joao
randy

I suggest that if the RIPE need another provider that they take time and issue a proper RFI/P/Q through the European Journal. It does ask an interesting question over disaster recovery in situations like this. Regards, Neil. -- Neil J. McRae - COLT neil@COLT.NET

Yes Neil, It should be interesting to know the 'official' requirements/recommendations for ccTLD's hosting For example: diversity geographical, network needs, security needs, building environment., etc Regards, Daniel Intelideas On Thursday 06 June 2002 15:59, Neil J. McRae wrote:
I suggest that if the RIPE need another provider that they take time and issue a proper RFI/P/Q through the European Journal. It does ask an interesting question over disaster recovery in situations like this.
Regards, Neil.

In message <200206061624.40230.dani@intelideas.com>, Daniel Concepcion writes:
Yes Neil,
It should be interesting to know the 'official' requirements/recommendations for ccTLD's hosting For example: diversity geographical, network needs, security needs, building environment., etc
The offcial requirements are: "No matter what, one of the servers will answer you." How you design and implement to that requirement, is your choice. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.

On Thu, Jun 06, 2002 at 04:24:40PM +0200, Daniel Concepcion wrote:
Yes Neil,
It should be interesting to know the 'official' requirements/recommendations for ccTLD's hosting For example: diversity geographical, network needs, security needs, building environment., etc
I've only been able to find a best practise guideline that specifies that the nameserver be online 24/7. (http://www.wwtld.org/ongoing/bestpractices/BestPractice_10Mar2001.html) I found it interesting to note that a significant number of cctld servers ignore the suggestions for root-servers in BCP40/RFC2870... "Other major zone server operators (gTLDs, ccTLDs, major zones) may also find it useful." and leave recursion enabled on the ccTLD servers (2.5) - the old ns.eu.net was one of these, I believe RIPE have done the right thing with the new one. What is even more disturbing is that there is a non-zero number of ccTLD servers that are still cache poisonable.

hi, On Thu, Jun 06, 2002 at 02:59:22PM +0100, Neil J. McRae wrote:
I suggest that if the RIPE need another provider that they take time and issue a proper RFI/P/Q through the European Journal. It does ask an interesting question over disaster recovery in situations like this.
Hmmm? As far as I can see, RIPE has enough providers. The problem is that the ccTLD secondary server hosted at KQ broke - which isn't RIPEs fault, and doesn't even host anything RIPE is master for (like ripe.net or the *.in-addr.arpa zones). Gert Doering -- NetMaster -- Total number of prefixes smaller than registry allocations: 45201 (45114) SpaceNet AG Mail: netmaster@Space.Net Joseph-Dollinger-Bogen 14 Tel : +49-89-32356-0 80807 Muenchen Fax : +49-89-32356-299

Gert,
On Thu, Jun 06, 2002 at 02:59:22PM +0100, Neil J. McRae wrote:
I suggest that if the RIPE need another provider that they take time and issue a proper RFI/P/Q through the European Journal. It does ask an interesting question over disaster recovery in situations like this.
Hmmm? As far as I can see, RIPE has enough providers. The problem is that the ccTLD secondary server hosted at KQ broke - which isn't RIPEs fault, and doesn't even host anything RIPE is master for (like ripe.net or the *.in-addr.arpa zones).
Hence why I said "if the RIPE need another provider". Note the part that has "if" in it. Regards, Neil.

At 16:35 +0200 6/6/02, Gert Doering wrote:
Hmmm? As far as I can see, RIPE has enough providers. The problem is that the ccTLD secondary server hosted at KQ broke -
ns.eu.net has not "broke". At least not yet. KPNQwest still has very competent people (and I would like to specifically thank Berislav Todorovic for embracing the idea of placing ns.eu.net outside KPNQwest to ensure stability and for all the support in actually doing it) The RIPE NCC doesn't currently need further support to operate the service, which is why we volunteered to do it, to provide a stable service until further steps are undertaken without the concern for the time period KPNQwest will be able to continue to operate. With time, since EUNet will not exist, ns.eu.net should also disappear (I am not quite sure the RIPE NCC would want to "own" the eu.net domain), but it should be after everyone has got time to think properly about a solution that suits them in the long term. Cheers, Joao

Very welcome, Thanks for this Dani it gives everyone much more breathing space. I think this a fantastic effort on behalf of the NCC, the folks at eu.net and anyone else involved, they should all be applauded for it. A few logistical questions that may be relevant to those affected. Is there a projected time when this service may be discontinued? I can imagine that the RIPE NCC doesn't want to indefinitely run secondary for end sites? If not: This is in the same AS as ns.ripe.net. Is it also physically on the same infrastructure? What I guess I'm asking is: To what extent do those using both ns.ripe.net and ns.eu.net have redundancy between the two servers? JC At 07:25 PM 6/5/2002 +0200, Daniel Diaz wrote:
Dear all,
Given the current situation of KPNQwest and the possibility of its services going offline sometime soon, the RIPE NCC in agreement with KPNQwest will be temporally hosting this server (ns.eu.net) in its premises.
This is to avoid major problems in the Internet as this server is secondary for a large number of ccTLD's zones, and thousand other zones.
We (AS3333) will be soon announcing the 192.16.202.0/24 prefix.
Trusting that this is welcome news.
Best regards.
-- RIPE NCC
-- Daniel.Diaz Operations Manager RIPE NCC

(cutting the list to reduce the noise). Hi John, Thanks. John L Crain <crain@icann.org> writes: * * This is in the same AS as ns.ripe.net. Is it also physically on the same * infrastructure? Basically yes. * What I guess I'm asking is: To what extent do those using both ns.ripe.net * and ns.eu.net have redundancy between the two servers? This is the reason Randy whines ;-). This is as I said *temporary*. During this interim, zones running in both servers would only get from it server redundancy. Regards. -- Daniel.Diaz RIPE NCC * JC * * * * At 07:25 PM 6/5/2002 +0200, Daniel Diaz wrote: * * >Dear all, * > * > * >Given the current situation of KPNQwest and the possibility * >of its services going offline sometime soon, the RIPE NCC in * >agreement with KPNQwest will be temporally hosting this * >server (ns.eu.net) in its premises. * > * >This is to avoid major problems in the Internet as this server * >is secondary for a large number of ccTLD's zones, and thousand * >other zones. * > * >We (AS3333) will be soon announcing the 192.16.202.0/24 prefix. * > * > * >Trusting that this is welcome news. * > * >Best regards. * > * >-- * >RIPE NCC * > * > * >-- * >Daniel.Diaz * >Operations Manager * >RIPE NCC * *

Daniel Diaz wrote:
Dear all,
Given the current situation of KPNQwest and the possibility of its services going offline sometime soon, the RIPE NCC in agreement with KPNQwest will be temporally hosting this server (ns.eu.net) in its premises.
This is to avoid major problems in the Internet as this server is secondary for a large number of ccTLD's zones, and thousand other zones.
Just for a note: The server ccTLD.tix.ch is available for all ccTLD's to add/expand diversity in location again. It is currently a secondary for the .CH and .LI ccTLD's and it is connected directly to the Zurich/Switzerland Internet Exchange TIX (http://www.tix.ch). It has got plenty of spare capacity and very good connectivity via many upstreams. -- Andre Oppermann TIX Project Manager W: http://www.tix.ch E: oppermann@tix.ch

On Wed, 5 Jun 2002, Daniel Diaz wrote: [cc list reduced to cut down noise] Should now be interesting to see how RIPE handles renumbering of this /24 within a 6 month period as per ripe-185. :-) ref: http://www.ripe.net/ripe/mail-archives/lir-wg/20020401-20020701/msg00228.htm... -Hank
Dear all,
Given the current situation of KPNQwest and the possibility of its services going offline sometime soon, the RIPE NCC in agreement with KPNQwest will be temporally hosting this server (ns.eu.net) in its premises.
This is to avoid major problems in the Internet as this server is secondary for a large number of ccTLD's zones, and thousand other zones.
We (AS3333) will be soon announcing the 192.16.202.0/24 prefix.
Trusting that this is welcome news.
Best regards.
-- RIPE NCC
-- Daniel.Diaz Operations Manager RIPE NCC

On Wed, Jun 05, 2002 at 07:25:47PM +0200, Daniel Diaz wrote:
Dear all,
Given the current situation of KPNQwest and the possibility of its services going offline sometime soon, the RIPE NCC in agreement with KPNQwest will be temporally hosting this server (ns.eu.net) in its premises.
This is to avoid major problems in the Internet as this server is secondary for a large number of ccTLD's zones, and thousand other zones.
We (AS3333) will be soon announcing the 192.16.202.0/24 prefix.
TDC is currently secondary for the dk TLD, if any other TLD need a secondary, please contact hostmaster@tele.dk and/or tgm@tdcinternet.dk best regards /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: FreeBSD committer @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them.
participants (13)
-
Andre Oppermann
-
Daniel Concepcion
-
Daniel Diaz
-
Gert Doering
-
Hank Nussbacher
-
Jan-Ahrent Czmok
-
Jesper Skriver
-
Joao Luis Silva Damas
-
John L Crain
-
John Payne
-
Neil J. McRae
-
Poul-Henning Kamp
-
Randy Bush