July 2001 - db-wg - mailman.ripe.net

<auto-dbm@ripe.net> is slow this afternoon.
by RIPE Database Administration 17 May '18

17 May '18

Dear Colleagues, Because of a very high level of use this afternoon, the response time of <auto-dbm(a)ripe.net> is longer than normal. I have made contact with those who are responsible and I expect the situation to improve as the machine works through the queue. Please be patient. Obviously we at the RIPE NCC Database Group are continuously working to make the performance of the database as good as possible. However, we cannot make improvements in zero time. We thank you for your co-operation up to now and we ask for your continued co-operation so that everyone receives the best possible service. If you have anymore questions, please contact <ripe-dbm(a)ripe.net>. Regards, Ambrose Magee ____________________________ RIPE Database Administration.

2 2

sub-allocations or something similar
by Dmitry Morozovsky 08 Aug '01

08 Aug '01

Hello there colleagues, for some last years I'm working with RIPE DB I think it would be useful to have some kind of "sub-allocation" inetnum objects. Brief example in our current situation: there is downstream provider behind us, currently without its own address block, so I've assigned /21 for them. All that space was of course well-documented, with ripe-141's covering all the nets, and appropriate inetnum objects have been created. But, for aggregating purposes, I suppose aggregating inetnum for the whole /21 would be useful and self-documenting. I can create such object, but such object is considered as overlapped. I think about explicit route-object also, but size behind current minimum allocation size (/19 for 195/8 or /20 for newer) somewhat stops me :) Your (both community and especially RIPE NCC people) suggestions are strongly expected ;-) Thank you. Sincerely, D.Marck [DM5020, DM268-RIPE, DM3-RIPN] ------------------------------------------------------------------------ *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck(a)rinet.ru *** ------------------------------------------------------------------------

4 4

Problems with Albanian Domains
by Elvis.Samson＠ernst-young.de 26 Jul '01

26 Jul '01

Hi, why is the albanian domain inima.al accessible through internet, but not listed in the ripe database? there are some european TLDs, where I couldn't find accessible websites in the ripe database. is there a reason for this or an error? regards and thanks for your help, elvis samson

2 1

RE: Problems with Albanian Domains
by Wilfried Woeber, UniVie/ACOnet 26 Jul '01

26 Jul '01

>why is the albanian domain inima.al accessible through internet, but not >listed in the ripe database? That is most probably due to the fact the RIPE DB is *not* an authoritative registry for (forward) domain names. While some TLD administrations indeed did use the RIPE-DB for some years to maintain a list of allocated/delegated domains, there was a major push during 2000 to remove (close to) all forward domain entries from the RIPE-DB. The RIEP-DB is still authortitative for the reverse Domains for address space that was distributed by way of the RIPE NCC. >there are some european TLDs, where I couldn't >find accessible websites in the ripe database. is there a reason for this >or an error? All TLD Administartors are welcome to register an object for the TLD itself - including a pointer to the whois server that in turn can answer queries. This mechanism is called "referral" and it works for some, but not for all, european TLDs. For an example how this looks like in reality, do a whois-query for e.g. $ whois -h whois.ripe.net -T domain unige.ch While this mechanism is available as an offer, neither the RIPE NCC nor the DB-WG have a mandate to urge TLD administrators to use that faciliy. >regards and thanks for your help, >elvis samson Just in case you want to follow up on Albanian domains, I'd suggest you get in touch with <Francesco.Gennai(a)iat.cnr.it> . This gentleman is listed as a contact in the SOA record for the TLD "AL". ______________________________________________________________________ bash$ nslookup Default Server: wsww.xx.xxxxxx.xx.at Address: 131.130.x.xxx > set q=soa > al. Server: wsww.xx.xxxxxx.xx.at Address: 131.130.x.xxx al origin = itgbox.iat.cnr.it mail addr = Francesco\.Gennai.iat.cnr.it [ ... ] ______________________________________________________________________ Best regards, -WW _________________________________:_____________________________________ Wilfried Woeber : e-mail: Woeber(a)CC.UniVie.ac.at UniVie Computer Center - ACOnet : Tel: +43 1 4277 - 140 33 Universitaetsstrasse 7 : Fax: +43 1 4277 - 9 140 A-1010 Vienna, Austria, Europe : RIPE-DB: WW144, PGP keyID 0xF0ACB369 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

Re: BOUNCE db-wg@ripe.net: Non-member submission from ["Zvezdelin Vladov" <zvezdi@langame.net>]
by RIPE NCC Staff 17 Jul '01

17 Jul '01

Dear Zvezdelin Vladov, This is indeed strange. Since both objects were created in the version 2 of the database, it is likely that there was a bug at some point that allowed the creation of duplicate nic-hdl in the database. As far as I know, this has not happened since version 3 went on-line 2001-04-23. Thanks for finding this - I'll contact the two people with the same nic-hdl and do what I can to help them straighten out the resulting mess (there are 456 objects that reference this nic-hdl!). If you have any more questions, please don't hesitate to contact <ripe-dbm(a)ripe.net>. Regards, Shane Kerr ____________________________ RIPE Database Administration. Original message: ---------------- From: "Zvezdelin Vladov" <zvezdi(a)langame.net> To: <db-help(a)ripe.net> Cc: <db-wg(a)ripe.net> Subject: strange person object???referenced, but does not exist? Date: Mon, 16 Jul 2001 16:25:21 +0200 Please, do the following query: whoisRIP -i tech-c KP389-RIPE This is person object of Kostantin Paeev, but at the end of the listing, you'll THE SAME NIC HDL NUMBER but for person: Katharina Potthoff When you look for this person Katharina, it does not exist in normal query. It this normal? for me this looks strange. Zvezdelin Vladov System&Network Manager AngelSoft Bulgaria Ph:+359 32 271209 Fax: +359 32 270934

2 1

bug in dictionary definition?
by unicorn＠Toledo.Kao.sm.net.ua 10 Jul '01

10 Jul '01

On Mon, 9 Jul 2001, RIPE Database Management wrote: > domain: Test-Forest.Od.UA > ... > nserver: 195.138.70.161 > ***Error: argument to nserver should be list [1:65535] of union DNS_name, rpsl_word. Does this complies `whois -v domain' information? It sais: > ... > nserver > > List of nameservers for a domain object; a minimum > of two is mandatory . > > <Fully qualified domain name(s) without trailing "."> > OR <IP Address(es) of the nameserver(s)> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > ... Whad do I have to place in `nserver field', in case I have no domain name at all? Is that `rpsl_word' should represent the reference to some another object describing my nameserver address? -- Sit Benedictum. Dragomiretsky Victor, Odessa Dept, KAM.

2 1

RE: Problems with WWW Whois ..
by RIPE NCC WebMaster 09 Jul '01

09 Jul '01

Hi Adam, >There seems to be another small bug in the WWW whois passer, >if you try to query for objects containing ':' (AS13646:RS-BOGONS-IN) >then you get the following output: The Whois arguments are invalid >( AS13646%3ARS-BOGONS-IN ). Please correct Cheers, > >Adam Thanks for the notification. We've mod_perl'ed the script to make it more efficient (you should see a great speed improvement in general) but one or two bugs have slipped though testing. We'll weed them out ASAP. On the near horizon is a completely new script with a somewhat more friendly interface. Regards, Lee Wilmot RIPE NCC p.s. could you please report problems to <webmaster(a)ripe.net> rather than to the working group, although I understand you were only replying to the original mail. Thanks :-)

1 0

RE: Problems with WWW Whois ...
by Low, Adam 06 Jul '01

06 Jul '01

Shane, There seems to be another small bug in the WWW whois passer, if you try to query for objects containing ':' (AS13646:RS-BOGONS-IN) then you get the following output: The Whois arguments are invalid ( AS13646%3ARS-BOGONS-IN ). Please correct Cheers, Adam

1 0

RIPE DB crash
by Magnus Karlsson 06 Jul '01

06 Jul '01

Yesterday there was a power outage at the NIKHEF. Following this outage the RIPE Database crashed. No objects or updates are lost! There is no need to resend your updates! The database will be fully restored during the day. All updates are queued and will be processed as soon as the database is fully restored. Thank you for your patience. -- Magnus Karlsson, RIPE NCC Database Group

2 1

Problems with WWW Whois ...
by Low, Adam 05 Jul '01

05 Jul '01

Hi, Is anybody working on the WWW whois on www.ripe.net ? I'm having inconsistent problems with numerous browsers, sometimes the query is successful but just as often I get an error message complaining about the URL and specifically the arguments passed to the script. It looks to me that someone's changed the code behind the submit button to add some trailing junk (submit=Submit) that the script cant pass. The Whois arguments are invalid ( AS13646&.submit=Submit+Query ). Please correct The Whois arguments are invalid ( AS13646&.submit= ). Please correct Anyone having problems with or have info ? Thanks, Adam

2 1

Publication of New RIPE Database Doc.
by Paul Rendek 03 Jul '01

03 Jul '01

Dear Colleagues, The RIPE NCC is pleased to announce that this week it will publish the "RIPE Database Reference Manual" on the RIPE NCC website. The new RIPE document is expected to answer many questions of Local Internet Registries and other users regarding the migration to version 3.0 of the RIPE Database software implemented on 23 April 2001. The new RIPE document obsoletes two previous documents: "RIPE Database Documentation Update" (ripe-189) and "RIPE Database Documentation" (ripe-157). The RIPE Database Reference Manual describes the functionality of the new version of the RIPE Database software that now uses the Routing Policy Specification Language (RPSL) to represent all database objects. RPSL defines an extended syntax for all database objects, mainly for the routing registry objects. Many new features have been implemented in this new version, such as Routing Policy System Security (RPSS) support specified in RFC 2725, fast IP lookups and automatic access control. RPSS provides authorisation mechanisms that enable a higher level of security for the Internet Routing Registries. Although the document is self-contained, it does not have examples of usage and illustrations of principles and concepts related to the RIPE Database functionality and implementation. This need will be filled by the "RIPE Database User's Manual" and the "RIPE Database Operations Manual" that are scheduled to be written. For more information and better understanding of the new document, the RIPE NCC encourages readers to brush up on RPSL (explained in RFC 2622), RPSS (explained in RFC 2725) and "Using RPSL in Practice" (the title of RFC 2650). Joao Luis Silva Damas, Chief Technical Officer of the RIPE NCC, wishes to acknowledge the contributions of past and present colleagues in the development of version 3.0 of the RIPE Database software: Andrei Robachevsky, Daniele Arena, Marek Bukowy, Engin Gunduz, Roman Karpiuk, Shane Kerr, A.M.R. Magee, Chris Ottrey and Filippo Portera. Paul Rendek RIPE NCC # # #

2 1