[arin-ppml] incorrect database info cause routing issue
Leo Vegoda
leo.vegoda at icann.org
Tue Feb 24 11:17:53 EST 2015
Mike Smith wrote:
[...]
> Following block has been assgined to Afrinic however it still shows
> ARIN block in the db.
>
> 45.160.0.0-45.255.255.255.
>
> Please check it and correct it.
45.160.0.0 - 45.191.255.255 was allocated to LACNIC in May last year
(https://www.iana.org/assignments/ipv4-recovered-address-space/ipv4-recovered-address-space.xhtml#ipv4-recovered-address-space-2)
and ARIN's whois server redirects to LACNIC's when queried for addresses in
that range:
$ whois -h whois.arin.net 45.160.0.0
[Querying whois.arin.net]
[Redirected to whois.lacnic.net]
[Querying whois.lacnic.net]
[whois.lacnic.net]
% Joint Whois - whois.lacnic.net
% This server accepts single ASN, IPv4 or IPv6 queries
It is only the second half of the 45.160.0.0 - 45.255.255.255 that is
allocated to AFRINIC.
Regards,
Leo Vegoda
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5475 bytes
Desc: not available
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20150224/12b280f1/attachment.p7s>
More information about the ARIN-PPML
mailing list