Hi Markus, On 07.01.20 at 21:19, Markus Lude wrote: > The server on the other hand could handle different record types, for > example "n ..." for network address space, but there are more. > If the record type is missing the server assumes (in this case) the > record type is n and notifies you of this assumption. > So it may be the other way around, "n " may be missing here in the > query to the ARIN whois server.
Okay, didn't know that at this time. Currently I know three query formats: whois on Linux: -V Md5.2 62.46.172.92 \r\n whois (sysinternals.com - Microsoft) on Windows -> This query doesn't like NIC.AT (invalid request): 62-46-172-92.ADSL.HIGHWAY.TELEKOM.AT\r\n whois on OpenBSD: 62.46.172.92\r\n > Compare the output of the following two: > > telnet whois.arin.net 43 > 62.46.172.92 > > which is also what you get with "whois 62.46.172.92" > and this: > > telnet whois.arin.net 43 > n 62.46.172.92 > > and if you want to see the mentioned help above: > > telnet whois.arin.net 43 > ? > > whois.apnic.net and whois.ripe.net understand "help" to display options. > > There seem to be no "standard" about options in queries to whois > servers. Okay, thanks! Nice, to learn something new. :)
