New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Confusing Whois
I always found it difficult understanding how to find the right path to get accurate whois information.
151.101.1.1, for example, is listed as US address on http://whois.domaintools.com/151.101.1.140 but 151/8 should be actually assigned to RIPE. RIPE's whois server does state that it belongs to NON-RIPE-NCC-MANAGED-ADDRESS-BLOCK but nowhere refers back to ARIN.
How would one go about finding the right whois server route - via port 43 - to get the correct information in this case but also in general?
Comments
I'm not sure what you mean but 151.101.0.0/16 is an ARIN subnet.
https://whois.arin.net/rest/net/NET-151-101-0-0-1
https://www.iana.org/whois?q=151.101.0.0
I just use the geektools whois proxy, since it knows where to direct you for all queries- whois.geektools.com
That is the question, how to know that
.
151/8 should generally go to RIPE.
https://www.gnu.org/software/jwhois/manual/jwhois.txt
See Note #5.
Thank you, from what I seem to understand from this configuration block is that it appears as if jwhois always starts at whois.arin.net and then traverses on depending on the response. That cant be the "proper" approach though, can it?
They all seem to work in the same way- but many hide the internal proxying and do a query themselves and just dump to stdout, because with new TLDs popping up nearly yearly, it's the most pragmatic way to manage it without having to build a new binary all of the time. They used to be hardcoded, but that eventually fell apart.
In my case I would not be concerned about domain lookups (and the implications with the "recent" TLD insanity) but only IPv4 addresses.
In this particular example my problem is that 151/8 is officially listed under RIPE but was semi-officially reassigned to ARIN (partially at least), but querying RIPE does not yield any ARIN reference. Thats why I wonder what the right approach would be. Could it be that whois.arin.net is actually what all the "others" (including DomainTools) query?
You'd still query RIPE. ARIN sends you right back to RIPE, anyhow.