- db-help - mailman.ripe.net

RIPE Test Database Issue
by Hujber Ádám 13 Jan '16

13 Jan '16

Dear Helping Center, I would like to learn how to use RIPE database. I downloaded some training guides and user manuals and I watched the video tutorials in Youtube. For this purpose I am using the test database. I created a person-maintainer pair (and separately these objects too) and I tested those objects. If I want to create the "inetnum" object with IP range 10.11.12.0 - 10.11.12.255, there is an error message at the top of the page: " Authorisation for parent [inetnum] 10.0.0.0 - 10.255.255.255 failed using "mnt-lower:" not authenticated by: TEST-DBM-MNT". In the older guide are password fields for the created mntner and for the parent mntner (TEST-DBM-MNT), and in the Youtube tutorial is the option to add passwords for the mntners, but I didn't fount these fields in the new version of RIPE. How can I add passwords for my mntner and for the parent mntner in the new version of RIPE? I attached screens from tutorials and from the error message. How long will my created objects remain in the database? I created some objects on Monday, but these aren't in the database today. Best Regards, Adam Hujber Üdvözlettel: Hujber Ádám Axian Kft. Tel.: +36/30-507-04-49

1 0

This db-help list will be discontinued
by Alex Band 18 Sep '15

18 Sep '15

Dear colleagues, We are going to discontinue this mailing list, db-help. If you would like to discuss something related to the RIPE Database, there are several options available: 1. For support or to submit bug report, please contact the RIPE NCC by visiting https://ripe.net/contact or send a message to ripe-dbm(a)ripe.net 2. To start a public discussion about the RIPE Database, for example about suggestions for functionality changes, best practices or operational usage, please subscribe to the RIPE Database Working Group mailing list: https://www.ripe.net/mailman/listinfo/db-wg/ This list will be disabled shortly. Kind regards, Alex Band RIPE NCC

2 1

FW: FAILED: arak1
by Javidi 09 Sep '15

09 Sep '15

Why does this object not create? 2.179.95.128 - 2.179.95.255 Error: inetnum parent has incorrect status: ASSIGNED PA But this is not coorect Please advise me Regards Reihane -----Original Message----- From: RIPE Database Administration local [mailto:unread@ripe.net] Sent: Tuesday, September 08, 2015 11:58 AM To: ripe(a)dci.ir Subject: FAILED: arak1 > From: Javidi <ripe(a)dci.ir> > Subject: arak1 > Date: Tue, 08 Sep 2015 10:27:40 +0200 > Reply-To: Javidi <ripe(a)dci.ir> > Message-ID: <002001d0ea18$1e780080$5b680180$(a)dci.ir> SUMMARY OF UPDATE: Number of objects found: 2 Number of objects processed successfully: 1 Create: 1 Modify: 0 Delete: 0 No Operation: 0 Number of objects processed with errors: 1 Create: 1 Modify: 0 Delete: 0 DETAILED EXPLANATION: ***Warning: Invalid keyword(s) found: arak1 ***Warning: All keywords were ignored ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The following object(s) were found to have ERRORS: --- Create FAILED: [inetnum] 2.179.95.128 - 2.179.95.255 inetnum: 2.179.95.128 - 2.179.95.255 netname: Telecommunication-of-Markazi descr: Telecommunication Company country: IR admin-c: AUTO-1 tech-c: AUTO-1 status: ASSIGNED PA mnt-by: AS12880-MNT changed: ripe(a)dci.ir 20150908 source: RIPE ***Error: inetnum parent has incorrect status: ASSIGNED PA ***Warning: Deprecated attribute "changed". This attribute will be removed in the future. ***Warning: Referenced person object aaa159-RIPE from mntner: AS12880-MNT is missing mandatory attribute "mnt-by:" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The following object(s) were processed SUCCESSFULLY: --- Create SUCCEEDED: [person] SM29689-RIPE soroush mazdak ***Warning: Deprecated attribute "changed". This attribute will be removed in the future. ***Warning: Referenced person object aaa159-RIPE from mntner: AS12880-MNT is missing mandatory attribute "mnt-by:" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The RIPE Database is subject to Terms and Conditions: http://www.ripe.net/db/support/db-terms-conditions.pdf For assistance or clarification please contact: RIPE Database Administration <ripe-dbm(a)ripe.net> Generated by RIPE WHOIS Update version 1.80.1 on DB-2 Handled email update (RIPE, 2015-09-08 10:27:57)

2 1

I: FAILED:
by Sergi Donata 28 Jul '15

28 Jul '15

Hi, We are trying to update an inetnum object add a line with the tech-c: MM27810-RIPE (nic-hdl of Mauro Mecci who is a technical contact of it.tim LIR) But it fails with error code (and a warning): ***Error: Authorisation for [inetnum] 213.230.128.0 - 213.230.159.255 failed using "mnt-by:" not authenticated by: RIPE-NCC-HM-MNT Can you help me to fix this? Thank you in advance Dona -----Messaggio originale----- Da: RIPE Database Administration local [mailto:unread@ripe.net] Inviato: martedì 28 luglio 2015 15:21 A: Sergi Donata Oggetto: FAILED: > From: Sergi Donata <donata.sergi(a)telecomitalia.it> > Subject: > Date: Tue, 28 Jul 2015 15:21:09 +0200 > Reply-To: Sergi Donata <donata.sergi(a)telecomitalia.it> > Message-ID: > <577095EC41519E4083F162934051091842A62EDB(a)telmba003ba020.telecomitalia > .local> SUMMARY OF UPDATE: Number of objects found: 1 Number of objects processed successfully: 0 Create: 0 Modify: 0 Delete: 0 No Operation: 0 Number of objects processed with errors: 1 Create: 0 Modify: 1 Delete: 0 DETAILED EXPLANATION: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The following object(s) were found to have ERRORS: --- Modify FAILED: [inetnum] 213.230.128.0 - 213.230.159.255 inetnum: 213.230.128.0 - 213.230.159.255 org: ORG-TIM1-RIPE netname: IT-TIM-20000516 descr: Telecom Italia Mobile descr: Provider Local Internet Registry country: IT admin-c: FP3192-RIPE tech-c: GF3559-RIPE tech-c: MM27810-RIPE status: ALLOCATED PA mnt-by: RIPE-NCC-HM-MNT mnt-lower: TIM-MNT mnt-routes: TIM-MNT changed: hostmaster(a)ripe.net 20000516 changed: hostmaster(a)ripe.net 20010202 changed: lir-help(a)ripe.net 20011214 changed: mmecci(a)mail.tim.it 20150728 created: 2001-12-14T18:40:18Z last-modified: 2004-04-17T14:56:25Z source: RIPE ***Error: Authorisation for [inetnum] 213.230.128.0 - 213.230.159.255 failed using "mnt-by:" not authenticated by: RIPE-NCC-HM-MNT ***Warning: Deprecated attribute "changed". This attribute will be removed in the future. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The following paragraph(s) do not look like objects and were NOT PROCESSED: Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie. This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail, Thanks. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The RIPE Database is subject to Terms and Conditions: http://www.ripe.net/db/support/db-terms-conditions.pdf For assistance or clarification please contact: RIPE Database Administration <ripe-dbm(a)ripe.net> Generated by RIPE WHOIS Update version 1.80.1 on DB-3 Handled email update (RIPE, 2015-07-28 15:21:25)

1 0

Using ripe.db
by Mads Nielsen 27 Jun '15

27 Jun '15

Hello. I have been searching for a guide to the ripe.db file. No luck. What's the format used for the database? Can i use ripe.db with the ripe whois client or server? Kind regards Mads Nielsen (Denmark)

1 0

Lots of failing updates for the last week(+)
by ripe＠foobar.dk 22 May '15

22 May '15

Mojn guys I see only FAILED updates for the last weeks - I've setup a simple check that counts the number of objects that failed and plots in a graph through Nagios. In the same script I notify if the number of successfully updated object equals zero. The reason for this is that I had (some years ago) a problem with NRTM dying on me and instead of logging in to the management console and run a "show dynamic", this workaround automatically gives me a warning if ex. NRTM is failing. The last succeeded update was on the 6th of May. This is what I see in the ripupdlogs since then: OurWhoisServer:/usr/local/whoisserver/var/log/ripupd# cat ripupdlog_RIPE.20150522 [cut...cut] 20150522 10:58:29 whois_rip-32246/1658837904 INFO [31250365] 0.00s FAILED [inetnum:][M:---] 20150522 10:58:29 whois_rip-32246/1658837904 INFO [31250366] 0.00s FAILED [person:][M:---] 20150522 10:58:29 whois_rip-32246/1658837904 INFO [31250367] 0.00s FAILED [domain:][M:---] 20150522 10:58:29 whois_rip-32246/1658837904 INFO [31250368] 0.00s FAILED [inet6num:][M:---] 20150522 10:58:29 whois_rip-32246/1658837904 INFO [31250369] 0.00s FAILED [inetnum:][M:---] 20150522 10:58:29 whois_rip-32246/1658837904 INFO [31250370] 0.00s FAILED [person:][M:---] 20150522 10:58:29 whois_rip-32246/1658837904 INFO [31250371] 0.00s FAILED [inetnum:][M:---] 20150522 10:58:29 whois_rip-32246/1658837904 INFO [31250372] 0.00s FAILED [inet6num:][M:---] 20150522 10:58:29 whois_rip-32246/1658837904 INFO ******** report ********** 20150522 10:58:29 whois_rip-32246/1658837904 INFO 0 objects OK ( 0.0000 obj/s) 20150522 10:58:29 whois_rip-32246/1658837904 INFO 8 objects failed 20150522 10:58:29 whois_rip-32246/1658837904 INFO average processing time 218.8603 obj/s (13131.62 obj/min) 20150522 10:58:29 whois_rip-32246/1658837904 INFO forwarded to serial:31250372 20150522 10:59:29 whois_rip-32246/1658837904 INFO connecting to NRTM server [whois.ripe.net:4444] (current serial=31250372) 20150522 10:59:29 whois_rip-32246/1658837904 INFO [31250373] 0.00s FAILED [person:][M:---] 20150522 10:59:29 whois_rip-32246/1658837904 INFO [31250374] 0.00s FAILED [inetnum:][M:---] 20150522 10:59:29 whois_rip-32246/1658837904 INFO [31250375] 0.00s FAILED [person:][M:---] 20150522 10:59:29 whois_rip-32246/1658837904 INFO [31250376] 0.00s FAILED [inetnum:][M:---] 20150522 10:59:29 whois_rip-32246/1658837904 INFO [31250377] 0.00s FAILED [domain:][M:---] 20150522 10:59:29 whois_rip-32246/1658837904 INFO [31250378] 0.00s FAILED [inetnum:][M:---] 20150522 10:59:29 whois_rip-32246/1658837904 INFO [31250379] 0.00s FAILED [person:][M:---] 20150522 10:59:29 whois_rip-32246/1658837904 INFO ******** report ********** 20150522 10:59:29 whois_rip-32246/1658837904 INFO 0 objects OK ( 0.0000 obj/s) 20150522 10:59:29 whois_rip-32246/1658837904 INFO 7 objects failed 20150522 10:59:29 whois_rip-32246/1658837904 INFO average processing time 221.1271 obj/s (13267.63 obj/min) 20150522 10:59:29 whois_rip-32246/1658837904 INFO forwarded to serial:31250379 20150522 11:00:29 whois_rip-32246/1658837904 INFO connecting to NRTM server [whois.ripe.net:4444] (current serial=31250379) 20150522 11:00:29 whois_rip-32246/1658837904 INFO [31250380] 0.00s FAILED [domain:][M:---] 20150522 11:00:29 whois_rip-32246/1658837904 INFO [31250381] 0.00s FAILED [role:][M:---] 20150522 11:00:29 whois_rip-32246/1658837904 INFO [31250382] 0.01s FAILED [aut-num:][M:---] 20150522 11:00:29 whois_rip-32246/1658837904 INFO [31250383] 0.00s FAILED [inetnum:][M:---] 20150522 11:00:29 whois_rip-32246/1658837904 INFO [31250384] 0.00s FAILED [aut-num:][M:---] 20150522 11:00:29 whois_rip-32246/1658837904 INFO ******** report ********** 20150522 11:00:29 whois_rip-32246/1658837904 INFO 0 objects OK ( 0.0000 obj/s) 20150522 11:00:29 whois_rip-32246/1658837904 INFO 5 objects failed 20150522 11:00:29 whois_rip-32246/1658837904 INFO average processing time 40.0275 obj/s (2401.65 obj/min) 20150522 11:00:29 whois_rip-32246/1658837904 INFO forwarded to serial:31250384 It looks like the updates after serial 31153170 are broken somehow: 20150506 21:25:12 whois_rip-14972/1712315280 INFO [31081490] 86.51s OK [person:DUMY-RIPE][M:ADD] 20150506 21:25:12 whois_rip-14972/1712315280 INFO [31081491] 0.25s OK [inetnum:37.58.121.224 - 37.58.121.231][M:ADD] 20150506 21:26:38 whois_rip-14972/1712315280 INFO [31081492] 85.62s OK [person:DUMY-RIPE][M:ADD] 20150506 21:26:38 whois_rip-14972/1712315280 INFO [31081493] 0.20s OK [inetnum:161.202.3.176 - 161.202.3.191][M:ADD] 20150506 21:28:03 whois_rip-14972/1712315280 INFO [31081494] 84.57s OK [person:DUMY-RIPE][M:ADD] 20150506 21:28:03 whois_rip-14972/1712315280 INFO [31081495] 0.29s OK [inetnum:169.54.135.96 - 169.54.135.127][M:ADD] 20150506 21:28:03 whois_rip-14972/1712315280 INFO [31081496] 0.20s OK [inetnum:130.193.84.240 - 130.193.84.247][M:ADD] 20150506 21:29:31 whois_rip-14972/1712315280 INFO [31081497] 88.34s OK [person:DUMY-RIPE][M:ADD] 20150506 21:29:32 whois_rip-14972/1712315280 INFO [31081498] 0.41s OK [inetnum:168.1.8.144 - 168.1.8.159][M:ADD] 20150506 21:29:33 whois_rip-14972/1712315280 INFO [31081499] 1.19s OK [as-set:AS-DECIX-CONNECTED][M:ADD] 20150506 21:29:34 whois_rip-14972/1712315280 INFO [31081500] 0.70s OK [as-set:AS-DECIX][M:ADD] 20150506 21:29:34 whois_rip-14972/1712315280 INFO ******** report ********** 20150506 21:29:34 whois_rip-14972/1712315280 INFO 1980 objects OK ( 0.0556 obj/s) 20150506 21:29:34 whois_rip-14972/1712315280 INFO 105 objects failed 20150506 21:29:34 whois_rip-14972/1712315280 INFO average processing time 0.0586 obj/s ( 3.51 obj/min) 20150506 21:29:34 whois_rip-14972/1712315280 INFO forwarded to serial:31081500 20150506 21:30:34 whois_rip-14972/1712315280 INFO connecting to NRTM server [whois.ripe.net:4444] (current serial=31081500) 20150506 21:30:34 whois_rip-14972/1712315280 INFO [31081501] 0.08s FAILED [as-set:][M:---] 20150506 21:30:34 whois_rip-14972/1712315280 INFO [31081502] 0.00s FAILED [as-set:][M:---] 20150506 21:30:34 whois_rip-14972/1712315280 INFO [31081503] 0.00s FAILED [as-set:][M:---] ... 20150506 21:45:19 whois_rip-14972/1712315280 INFO 630 objects OK ( 0.7115 obj/s) 20150506 21:45:19 whois_rip-14972/1712315280 INFO 71040 objects failed 20150506 21:45:19 whois_rip-14972/1712315280 INFO average processing time 80.9461 obj/s (4856.77 obj/min) 20150506 21:45:19 whois_rip-14972/1712315280 INFO forwarded to serial:31153170 20150506 21:46:19 whois_rip-14972/1712315280 INFO connecting to NRTM server [whois.ripe.net:4444] (current serial=31153170) Does any of you see the same thing in your logs ? And does any of you have an idea about what's going wrong with the updates ? Best regards, Peter Landbo

1 0

Change MNTNER handle?
by Rottmann, Ralf 03 Dec '14

03 Dec '14

Hi there, Is it at all possible to change an existing MNTNER handle? It appears to be read-only when I try to update through Ripe's web forms. Sorry for asking such a newbie question but I wonder whether this is possible, perhaps through a support request to Ripe. Best, -Ralf

1 0

change maintainer
by Evgeny Belyaev 18 Nov '14

18 Nov '14

Hello dear RIPE-DB administrators! We are LIR RU.GPT (Garant-Park-Telecom Ltd.) We use a range of addresses 195.24.64.0/21 (ASSIGNED_PI) And we have difficulty with the administration of the following domain objects: 65.24.195.in-addr.arpa mnt-by PAN1-RIPE-MNT 66.24.195.in-addr.arpa mnt-by PAN1-RIPE-MNT 67.24.195.in-addr.arpa mnt-by PAN1-RIPE-MNT 70.24.195.in-addr.arpa mnt-by PAN1-RIPE-MNT 71.24.195.in-addr.arpa mnt-by PAN1-RIPE-MNT mntner: PAN1-RIPE-MNT descr: Maintains all objects PAN-RIPE admin-c: PAN-RIPE tech-c: PAN-RIPE auth: MD5-PW # Filtered mnt-by: PAN1-RIPE-MNT referral-by: PAN1-RIPE-MNT source: RIPE # Filtered person: Alexander V Panov address: MSU, Science Park, Garant-Park-Telecom address: Moscow address: Russia remarks: phone: +7 095 7898207 phone: +7 495 7898207 remarks: fax-no: +7 095 9308800 fax-no: +7 495 9308800 nic-hdl: PAN-RIPE mnt-by: PAN1-RIPE-MNT source: RIPE # Filtered remarks: modified for Russian phone area changes Alexander V Panov no longer works at the company Garant-Park-Telecom Ltd. Please help us change maintainer in domain objects: 65.24.195.in-addr.arpa 66.24.195.in-addr.arpa 67.24.195.in-addr.arpa 70.24.195.in-addr.arpa 71.24.195.in-addr.arpa from PAN1-RIPE-MNT to AS5537-MNT. -- With best regards, Evgeny Belyaev e-mail: belyaev(a)hostcomm.ru Network Operations Center phone: +7(495)737-7646 RU-CENTER Group

2 1

previous registration for 217.33.191.128/27
by Stephen Barker 24 Oct '14

24 Oct '14

Good Morning, I have a customer that is requesting a large block of IPs and has advised that they are/ have returned the below address block. They did state that they believe it has been re-assigned. Would anyone be able to advise how I can check the history of the allocations of this range? The customer is Brightside Group. 217.33.191.128/27 Current DB information; inetnum: 217.33.191.128 - 217.33.191.159<https://apps.db.ripe.net/search/lookup.html?source=ripe&key=217.33.191.128%…> netname: EDEVELOPMENT descr: FTIP003191590 eDevelopment Ltd country: GB admin-c: CG5480-RIPE<https://apps.db.ripe.net/search/lookup.html?source=ripe&key=CG5480-RIPE&typ…> tech-c: CG5480-RIPE<https://apps.db.ripe.net/search/lookup.html?source=ripe&key=CG5480-RIPE&typ…> status: ASSIGNED PA mnt-by: BTNET-MNT<https://apps.db.ripe.net/search/lookup.html?source=ripe&key=BTNET-MNT&type=…> mnt-lower: BTNET-MNT<https://apps.db.ripe.net/search/lookup.html?source=ripe&key=BTNET-MNT&type=…> mnt-routes: BTNET-MNT<https://apps.db.ripe.net/search/lookup.html?source=ripe&key=BTNET-MNT&type=…> remarks: Please send abuse notification to abuse(a)bt.net<mailto:abuse@bt.net> remarks: Please send delisting issues to btnetdns(a)bt.net<mailto:btnetdns@bt.net> remarks: This range is statically assigned source: RIPE # Filtered Thanks Steve

2 1

Fwd: [ripe.net #1140111] AutoReply: API Country resource incongruency
by Enzo Ghinazzi 13 Oct '14

13 Oct '14

Not sure if right place here and followed notification procedure to stat(a)ripe.net [ticket #1140111]... I've found some *missing prefix/asn* returned from query to COUNTRY RESOURCE https://stat.ripe.net/data/country-resource-list/data.json?resource=it It seems that response list is missing all those ipv4 resource lines that before were returned as RANGE instead of CIDR, and obviously related asn. For example 151.3.0.0/16 is related to country IT ( https://stat.ripe.net/data/whois/data.json?resource=151.3.0.0/16) but* this prefix and its ASN is missing in response country resource list* of above query. Earlier ,sure at 13 JUL 2014, this prefix was in response as contained in range 151.3.0.0-151.84.255.255. Regards,

1 0