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/ipv6-wg@ripe.net/
[ipv6-wg at ripe.net] inet6num missing for allocation - more?
- Previous message (by thread): [ipv6-wg at ripe.net] inet6num missing for allocation - more?
- Next message (by thread): [ipv6-wg at ripe.net] inet6num missing for allocation - more?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
leo vegoda
leo at ripe.net
Wed Aug 4 20:40:16 CEST 2004
Hi Daniel, On Aug 4, 2004, at 8:30 pm, Daniel Roesen wrote: > I've just noticed, that the allocation 2001:478::/32 is not registered > in the RIPE DB: > > $ whois -h whois.ripe.net -r 2001:478::/32 | fgrep inet6num: > inet6num: 0::/0 > > Could RIPE check wether this problem does exist for other allocations > too? Or is EP.NET "special"? :-) This /32 appears to come from 2001:0400::/23 which is allocated to ARIN. You can query the ARIN database directly to see contact information for EP.NET. However, you can also find basic contact information (and the fact that the block is allocated) by querying the RIPE database using the -a flag: $ whois -h whois.ripe.net -a 2001:478::/32 This gives you information from all the databases mirrored by whois.ripe.net. Kind regards, -- leo vegoda Registration Services Manager RIPE NCC
- Previous message (by thread): [ipv6-wg at ripe.net] inet6num missing for allocation - more?
- Next message (by thread): [ipv6-wg at ripe.net] inet6num missing for allocation - more?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]