-
Notifications
You must be signed in to change notification settings - Fork 112
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.
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
APNIC IP inter RIR transfert not properly handled #95
Comments
I am not sure, since this would require parsing free-form text. Do you want to try? |
I'm not C skilled myself, I'll dig around internally if there's a C master to propose a PR |
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,
Just chucked a pretty small and safe PR here: #152 that will solve the whois for all APNIC space that has been transferred out. |
as i now came over this (49.12.0.0 - 49.13.255.255) it would be nice if whois could support this. |
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:
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 ?
The text was updated successfully, but these errors were encountered: