This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
[db-wg] Broken RDAP response
- Previous message (by thread): [db-wg] Broken RDAP response
- Next message (by thread): [db-wg] Broken RDAP response
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Piotr Strzyzewski
Piotr.Strzyzewski at polsl.pl
Thu Aug 9 20:00:40 CEST 2018
On Thu, Aug 09, 2018 at 07:33:40PM +0200, Christoffer Hansen via db-wg wrote: > On Thu, 9 Aug 2018 at 18:20, Brian Rak via db-wg <db-wg at ripe.net> wrote: > > > > We hit issues with: https://rdap.db.ripe.net/ip/37.246.0.0/16 > > > > It looks like someone added multiple country: fields in the RIPE database > > > > inetnum: 37.246.0.0 - 37.246.255.255 > > netname: MD-SHATRANS-20120417 > > country: GB > > country: US > > org: ORG-TS151-RIPE > > > > How did this even get into the database in the first place? I'm not > > sure returning an error via RDAP is really the best way of handling this. > > Looks like several INETNUM objects have more than 1 country code > attached in the RIPE NCC database. :/ $ whois -t inetnum |grep country country: [mandatory] [multiple] [ ] That should explain things a bit. Piotr -- Piotr Strzyżewski Silesian University of Technology, Computer Centre Gliwice, Poland
- Previous message (by thread): [db-wg] Broken RDAP response
- Next message (by thread): [db-wg] Broken RDAP response
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]