Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

APNIC IP inter RIR transfert not properly handled #95

Open
bressiers opened this issue Feb 8, 2021 · 5 comments · May be fixed by #152
Open

APNIC IP inter RIR transfert not properly handled #95

bressiers opened this issue Feb 8, 2021 · 5 comments · May be fixed by #152

Comments

@bressiers
Copy link

bressiers commented Feb 8, 2021 •
edited

Hello folks,
Seems an IP range transfert from APNIC to at least RIPE, but probably to any other RIR they have agreements with, is not properly handled on whois response, as not yet managed on the exceptions.
for example:

whois 1.179.112.0

returns:

% for more information on IANA, visit http://www.iana.org
% This query returned 1 object

refer:        whois.apnic.net

inetnum:      1.0.0.0 - 1.255.255.255
organisation: APNIC
status:       ALLOCATED

whois:        whois.apnic.net

changed:      2010-01
source:       IANA

# whois.apnic.net

% [whois.apnic.net]
% Whois data copyright terms    http://www.apnic.net/db/dbcopyright.html

% Information related to '1.179.112.0 - 1.179.127.255'

% Abuse contact for '1.179.112.0 - 1.179.127.255' is '[email protected]'

inetnum:        1.179.112.0 - 1.179.127.255
netname:        STUB-1-179-112SLASH20
descr:          Transferred to the RIPE region on 2020-12-08T07:54:04Z.
country:        ZZ
admin-c:        STUB-AP
tech-c:         STUB-AP
status:         ALLOCATED PORTABLE
mnt-by:         APNIC-STUB
mnt-irt:        IRT-STUB-AP
last-modified:  2020-12-07T22:00:28Z
source:         APNIC

The APNIC has implemented, back in 2019, "stub" records (link to their blog) , that returns the information related to an inter RIR transfert, and the destination can be found with:
descr: Transferred to the RIPE region on 2020-12-08T07:54:04Z.

Would be an interesting improvement I guess to follow such redirection ?
@rfc1036
Copy link
Owner

rfc1036 commented Feb 8, 2021

I am not sure, since this would require parsing free-form text. Do you want to try?

@bressiers
Copy link
Author

I'm not C skilled myself, I'll dig around internally if there's a C master to propose a PR

@rfc1036
Copy link
Owner

rfc1036 commented Jun 6, 2021

I have downloaded ftp://ftp.apnic.net/apnic/whois/apnic.db.inetnum.gz and there are only 231 inetnum objects with that comment, so this does not look like something urgent to implement.

@rfc1036 rfc1036 mentioned this issue Jan 3, 2022
Closed
@zappiehost zappiehost linked a pull request Aug 23, 2023 that will close this issue
Open
@zappiehost
Copy link

I have downloaded ftp://ftp.apnic.net/apnic/whois/apnic.db.inetnum.gz and there are only 231 inetnum objects with that comment, so this does not look like something urgent to implement.

The list is growing more and more as IPs are getting transferred cross RIRs,

$ zgrep "Transferred to the" apnic.db.inetnum.gz | wc -l
606

Just chucked a pretty small and safe PR here: #152 that will solve the whois for all APNIC space that has been transferred out.

@C0RD
Copy link

C0RD commented Dec 25, 2023

as i now came over this (49.12.0.0 - 49.13.255.255) it would be nice if whois could support this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Support APNIC inter-RIR IPv4 transfer whois referrals zappiehost/whois
4 participants
@rfc1036 @C0RD @bressiers @zappiehost