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/[email protected]/
[db-wg] RIPE DB missing inetnum referral for 204/8 (and others) to ARIN?
- Previous message (by thread): [db-wg] RIPE DB missing inetnum referral for 204/8 (and others) to ARIN?
- Next message (by thread): [db-wg] RIPE DB missing inetnum referral for 204/8 (and others) to ARIN?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Shane Kerr
shane at ripe.net
Wed Dec 10 14:54:39 CET 2003
Daniel Roesen wrote: > Hi, > > $ whois -h whois.ripe.net 204.152.184.85 > [...] > inetnum: 0.0.0.0 - 255.255.255.255 > netname: IANA-BLK > descr: The whole IPv4 address space > [...] > > and nothing else. The referral to ARIN for 204/8 is missing. > I've checked a couple of other RIRs /8s which all had the same problem. > > Was there a deliberate change that I missed? The RIPE Database keeps information about resources in the RIPE NCC service region, as well as routing registry records. The RIPE NCC does not maintain information about resources managed by other RIRs. Users wishing to know which RIR is responsible for a given /8 should consult the IANA: http://www.iana.org/assignments/ipv4-address-space Providing this information via a Whois interface is a service the RIRs are considering for the NRO structure. -- Shane Kerr Software Engineering Group Manager RIPE NCC
- Previous message (by thread): [db-wg] RIPE DB missing inetnum referral for 204/8 (and others) to ARIN?
- Next message (by thread): [db-wg] RIPE DB missing inetnum referral for 204/8 (and others) to ARIN?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]