- db-wg - mailman.ripe.net

Attn. NRTM clients: Missing serial files
by RIPE Database Manager 29 Feb '00

29 Feb '00

Dear Colleagues, Due to a filesystem problem, 30605 serial files were not written. The missing range is 8929802-8930406. Unfortunately to continue near real-time mirroring of the RIPE database, you will need to resync with the RIPE database. The new snapshot of the database will be available tonight (at 1 a.m. CET, 1 March). This problem does not affect the queries and the RIPE databse consistency. Sorry for trouble and inconvenience. If you have any further questions, please do not hesitate to contact <ripe-dbm(a)ripe.net> Regards, Andrei Robachevsky ____________________________ RIPE Database Administration.

1 0

inetnum conversion
by Engin Gunduz 28 Feb '00

28 Feb '00

Dear colleagues, RIPE NCC will be converting the legacy inetnum objects which are in old classful notation into classless range notation. We provide the list of inetnum objects to be converted during this process at: http://www.ripe.net/ripencc/pub-services/db/in_conversion/ There are 16404 such inetnums in the RIPE whois database, so we have divided them in four parts, but the list is available also as a big single file. The list contains the classful notation, new classless notation and the netname of the inetnums. The conversion is planned to take place on 26-27 February. You can check the list for your inetnum objects. If you detect a problem, please contact <ripe-dbm(a)ripe.net>. Also, please send your comments about the conversion to the list, Regards, Engin Gunduz RIPE NCC Database Group -----------------------

1 2

Re: RIPE DB service restored
by Janos Zsako 23 Feb '00

23 Feb '00

> From owner-lir-wg(a)ripe.net Wed Feb 23 13:47:01 2000 > From: Nils Jeppe <nils(a)work.de> Dear Nils, > Yes, one question; why haven't you announced taking down the DB? I find > this unacceptable, some of us have to work with it you know? We have > customers which need new Person objects, new Domains, etc. etc. Now, I > understand perfectly if there are emergency maintainances or whatever, but > don't just switch it off for an entire day without at least letting us > know! How much effort would it have been if you had written a seven line > email explaining that you have to take the DB down, and why? > > It's not like you're some kind of Internet Dictatorship or IP God which > can do as it pleases; the RIPE NCC takes care of this stuff on the behalf > of the LIRs and is financed by the LIRs, so this heavy-handed approach is > really not something I appreciate. I guess the RIPE community in general does not appreciate YOUR approach (at least I do not). :(( Please find below the mail the RIPE NCC sent out BEFORE they turned updates off. I guess you have not been at the RIPE meetings and did not follow the work the RIPE NCC has been doing in the last many years. Otherwise I do not think you would make a remark like the above. Best regards, Janos > > > Best wishes, > Nils Jeppe > > > On Tue, 22 Feb 2000, RIPE Database Administration wrote: > > > > > Dear Colleagues, > > > > We wish to announce that the whois and update service > > of the RIPE Database has returned to normal. Currently, the > > queue of updates is being processed. We expect this queue to > > be cleared later this evening. > > > > Thank you for being patient. You will find that the service > > level of the RIPE Database has been improved. If you > > have questions, please contact <ripe-dbm(a)ripe.net>. > > > > If you have any questions, please don't hesitate > > to contact <ripe-dbm(a)ripe.net>. > > > > Regards, > > > > Daniele Arena > > ____________________________ > > RIPE Database Administration. > > > > ----- Begin Included Message -----

4 3

RIPE DB service restored
by RIPE Database Administration 22 Feb '00

22 Feb '00

Dear Colleagues, We wish to announce that the whois and update service of the RIPE Database has returned to normal. Currently, the queue of updates is being processed. We expect this queue to be cleared later this evening. Thank you for being patient. You will find that the service level of the RIPE Database has been improved. If you have questions, please contact <ripe-dbm(a)ripe.net>. If you have any questions, please don't hesitate to contact <ripe-dbm(a)ripe.net>. Regards, Daniele Arena ____________________________ RIPE Database Administration.

2 1

Updates to the RIPE whois database stopped
by RIPE Database Administration 21 Feb '00

21 Feb '00

Dear All, Due to a crash of our whois server which we experienced last Saturday we are stopping the updates tonight and we are going to reindex the data. There is no need to resend your updates. The updates will be queued and they will be resumed tomorrow. We are also going to upgrade the main server so that it can cope better with the ever growing load. The whois query service will be switched to our backup server, therefore the response time will be slower than usual. If you have any questions, please don't hesitate to contact <ripe-dbm(a)ripe.net>. Regards, Marek Bukowy ____________________________ RIPE Database Administration.

1 0

Next step in the RIPE database reimplementation project
by RIPE Database Administration 21 Feb '00

21 Feb '00

Dear all, This is to notify you of the further steps in the development of the new RIPE Database. Today we have put online the next version of the reimplemented whois server. It is running on the machine reimp.ripe.net on port 43. This server is running as a near real-time mirror client, mirroring the current RIPE database. Please have a look and let us know if you find anything wrong. The results of the queries are supposed to match the results of the queries from our production server. Please note that the access control mechanism may prevent you from obtaining excessive contact information. Please contact <ripe-dbm(a)ripe.net> if the limit turns out to be too small for your tests. Please send your comments and bug reports to <db-beta(a)ripe.net> mailing list. To subscribe to this list send a message to <majordomo(a)ripe.net> with the line: subscribe db-beta in the body of your letter. This is a moderated mailing list so some delays in subscription are possible. The source code is also being released. It can be found at our ftp site: ftp://ftp.ripe.net/ripe/dbase/reimp/RIP-0.2.0beta2.tar.gz The instructions for installing the software and loading the database can be found in the file INSTALL in the main directory. Best regards, Daniele Arena ____________________________ RIPE Database Administration.

1 0

RIPE Database usage
by Wolf-Guido Lutz 18 Feb '00

18 Feb '00

Hello List, forgive me if this is a question that doesn't belong here, but maybe someone can point me in the right direction. I have started maintaining my own nameserver a few months ago and the company that does the second level domain connections for me doesn't seem to be able to help me with this: how can I change the information in the maintainer object of my own RIPE record? In fact, I would like to create my own maintainer object. Is there any documentation maybe on who/how to change that information in the RIPE database? TIA Wolf-Guido Lutz

3 2

Top 100 Maintainers List 20000217
by RIPE Database Administration 17 Feb '00

17 Feb '00

1 0

1. Draft, proposed agenda DB-WG meeting RIPE-35, Thu.,Feb.24 2000
by Wilfried Woeber, UniVie/ACOnet 15 Feb '00

15 Feb '00

Dear DB-WG! Attached please find the 1st draft: Proposed Agenda for the DB-WG Meeting during RIPE35, Amsterdam. As always, comments and proposals for additional topics are welcome. There might be last-minute changes, so stay tuned (this time we've been less successful in finding an optimal solution for the scheduling maze)! Regards, and see you in Amsterdam, Wilfried. ______________________________________________________________________ Proposed Agenda for the Database Working Group Meeting RIPE-35, February 2000, Amsterdam, NL 1. Draft Note: for any updates between now and just before the WG meeting, watch the DB WG Mailing List, please! Slot #1, Thursday, Feb. 24th, 09:00 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A. Administrative stuff (Wilfried Woeber, chair) B. RIPE DB, operational update (NCC: AMRM, 20min.) C. A short review on the maintainer mechanism - are there any security concerns? D. (tentatively) Is there an interest to register CERT/IRT-related info? - brainstorming/proposals Slot #2, Thursday, Feb. 24th, 11:00 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ E. Status of the reimplementation project (NCC: JLSD, 20min.) F. Transition to ripe db v3.0 and transition TF (JLSD & WW, 15min G. Do we need/want a DB WG review/re-structuring? - future topics of interest (workplan/charter?) - I/O with other WGs - logistics Y. Input from other WGs - t.b.d. Z. AOB ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ WW, 15-FEB-2000 17:23:23 -------------------------------------------------------------------------- Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Vienna University : Fax: +43 1 4277 - 9 140 Universitaetsstrasse 7 : RIPE-DB (&NIC) Handle: WW144 A-1010 Vienna, Austria, Europe : PGP public key ID 0xF0ACB369 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Common sense requires a common language... __________________________________________________________________________

1 0

Whoisd buffer overrun
by RIPE Database Administration 03 Feb '00

03 Feb '00

Dear colleagues, It was brought to our attention last night that the perl whoisd server the RIPE NCC is currently running is vulnerable to a buffer overflow attack. We have taken action immediately and fixed this problem on our production servers. We have also checked for traces of people taking advantage of the vulnerability and concluded that this was not the case. The whois service was not affected. Should you be running a copy of our software, please apply the patch attached below to bin/whoisd. It truncates the query to 255 characters. If you have any questions or comments, please contact <ripe-dbm(a)ripe.net>. We would like to thank Geert Jan de Groot and Steve Bellovin for bringing this to our attention. Kind Regards, Mirjam Kuehne Head External Services RIPE NCC -------------------- 1. save the following text as /tmp/whoisdpatch ----------cut here------------------------------ *** whoisd.trunc Wed Feb 2 22:28:34 2000 --- whoisd Wed Feb 2 22:29:46 2000 *************** *** 1679,1694 **** $query=join(" ", @ARGV); } else { - my($trunclen); - alarm $KEEPOPEN if (!$commandline); $query=<$input>; - - # truncate to 255 chars - $trunclen = length($query); - $trunclen = 255 if $trunclen > 255; - substr( $query, $trunclen ) = ""; - } # &dpr("query: -$query- errorcode: -$!-\n"); --- 1679,1686 ---- ----------cut here-------------------------------- 2. execute in the directory where your whoisd lives: $ patch < /tmp/whoisdpatch

3 2