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.

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

Support for segment and RIPE handle lookups #451

Open
martin-schmidt opened this issue Nov 6, 2015 · 0 comments
Open

Support for segment and RIPE handle lookups #451

martin-schmidt opened this issue Nov 6, 2015 · 0 comments
Labels

Comments

@martin-schmidt
Copy link

Besides the retrieval of fqdn related data (registrar, etc.) WHOIS is responsible for providing AS- und IP-information. There is lookup support for IP addresses but not for network segments and RIPE handles. client.lookup('5.9.232.64/29') throws Whois::ServerNotFound: Unable to find a WHOIS server for '5.9.232.64/29', but the expected behavior is to fetch the network related information from RIPEs WHOIS database like the Linux client does it (update: I RTFM and the manpage says: "When querying whois.arin.net for IPv4 or IPv6 networks, the CIDR netmask length will be automatically removed from the query string." Implementing this could be tricky, because RIPE servers support netmasks, ARIN servers respond with No match found):

whois 5.9.232.64/29
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf

% Note: this output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to '5.9.232.64 - 5.9.232.71'

% Abuse contact for '5.9.232.64 - 5.9.232.71' is '[email protected]'

inetnum:        5.9.232.64 - 5.9.232.71
netname:        ETESPA-LLC
descr:          ETESPA LLC
country:        DE
admin-c:        RT5676-RIPE
tech-c:         RT5676-RIPE
status:         ASSIGNED PA
mnt-by:         HOS-GUN
created:        2014-03-27T10:40:05Z
last-modified:  2014-03-27T10:40:05Z
source:         RIPE # Filtered

person:         Roberto Todeschini
address:        ETESPA LLC
address:        113 Barksdale Professional Center
address:        19711 Newark
address:        UNITED STATES
phone:          +41788303850
nic-hdl:        RT5676-RIPE
mnt-by:         HOS-GUN
created:        2013-12-12T08:06:12Z
last-modified:  2013-12-12T08:06:12Z
source:         RIPE # Filtered

% Information related to '5.9.0.0/16AS24940'

route:          5.9.0.0/16
descr:          HETZNER-RZ-FKS-BLK5
origin:         AS24940
mnt-by:         HOS-GUN
created:        2012-04-26T10:30:12Z
last-modified:  2012-04-26T10:30:12Z
source:         RIPE # Filtered

% This query was served by the RIPE Database Query Service version 1.82 (DB-1)

WHOIS records refer to entity related information using RIPE handles (the record above contains RT5676-RIPE) which can be resolved.

whois RT5676-RIPE
% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf

% Note: this output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to 'RT5676-RIPE'

person:         Roberto Todeschini
address:        ETESPA LLC
address:        113 Barksdale Professional Center
address:        19711 Newark
address:        UNITED STATES
phone:          +41788303850
nic-hdl:        RT5676-RIPE
mnt-by:         HOS-GUN
created:        2013-12-12T08:06:12Z
last-modified:  2013-12-12T08:06:12Z
source:         RIPE # Filtered

% This query was served by the RIPE Database Query Service version 1.82 (DB-1)

But record = client.lookup('RT5676-RIPE') throws Whois::ServerNotFound: Unable to find a WHOIS server for 'rt5676-ripe', because RIPE handles are not supported.
That's why domain owners don't need to change the contact information for every domain they own if their phone number or address changes, but only need to update the specific handle.

Supporting RIPE handles would make it easier to normalize and store the fetched information and helps to maintain their consistency.

@martin-schmidt martin-schmidt changed the title Feature: Support for segment and handle lookups Feature: Support for segment and RIPE handle lookups Nov 6, 2015
@weppos weppos added the feature label Dec 3, 2021
@weppos weppos changed the title Feature: Support for segment and RIPE handle lookups Support for segment and RIPE handle lookups Dec 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants