RIPE DB missing inetnum referral for 204/8 (and others) to ARIN?
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? Best regards, Daniel
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
On Wed, Dec 10, 2003 at 02:54:39PM +0100, Shane Kerr wrote:
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.
Well, but if I'm not totally mistaken, RIPE DB contained referrals for /8s of other RIRs until recently. Am I wrong in this memory? Regards, Daniel
Daniel Roesen wrote:
On Wed, Dec 10, 2003 at 02:54:39PM +0100, Shane Kerr wrote:
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.
Well, but if I'm not totally mistaken, RIPE DB contained referrals for /8s of other RIRs until recently. Am I wrong in this memory?
We only have on-line history of the RIPE Database going back to April 2001, which is when we started using version 3 of the software. (Older records are stored in off-line media.) Since April 2001, there has not been a record for the 204.0.0.0/8, but there may have been before. Also, to be clear, the RIPE Database has a feature where domain records can be used to direct the RIPE Whois server to query another database for a domain record. This is done by adding a "refer:" attribute to the domain object. For example: domain: DE . . . refer: ClientAddress whois.denic.de 43 . . . This means that when users query for any DE domain, the query will get sent to "whois.denic.net", unless they explicitly disable this feature with the "-R" flag. This attribute is only present in domain objects, and AFAIK has never been in any other object types. -- Shane Kerr RIPE NCC
On Wed, Dec 10, 2003 at 03:31:10PM +0100, Shane Kerr wrote:
Well, but if I'm not totally mistaken, RIPE DB contained referrals for /8s of other RIRs until recently. Am I wrong in this memory?
We only have on-line history of the RIPE Database going back to April 2001, which is when we started using version 3 of the software. (Older records are stored in off-line media.)
Since April 2001, there has not been a record for the 204.0.0.0/8, but there may have been before.
Uhm. Then I'm probably just getting senile. Thanks for checking! I could have sworn that there were "dummy" objects pointing to the other RIRs. "This block has been allocated to ARIN/APNIC/...". Best regards, Daniel
Daniel Roesen wrote:
On Wed, Dec 10, 2003 at 02:54:39PM +0100, Shane Kerr wrote:
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.
Well, but if I'm not totally mistaken, RIPE DB contained referrals for /8s of other RIRs until recently. Am I wrong in this memory?
One of our engineers here points out that maybe you are talking about the other sources that we mirror in the Database. You can query all sources that we mirror via the "-a" flag on a query: $ whois -a 204/8 You can also query only ARIN, by the "-s" flag: $ whois -s arin 204/8 Finally, you can see all the sources we mirror by using "-q sources": $ whois -q sources -- Shane Kerr RIPE NCC p.s. Thanks for the observation, Can!
participants (2)
-
Daniel Roesen -
Shane Kerr