parms for simple answer
is there no parm to whois which results only in the specific answer, not also the org: person: and grandmother: objects? i want it irrespective of object type i am looking up. ``` whois -h whois.ripe.net -r -T inetnum 147.28.0.0/16 | egrep -v '^($|%)' ``` is opbject-type specific randy
Randy, On 27/08/2019 09.48, Randy Bush via db-wg wrote:
is there no parm to whois which results only in the specific answer, not also the org: person: and grandmother: objects? i want it irrespective of object type i am looking up.
``` whois -h whois.ripe.net -r -T inetnum 147.28.0.0/16 | egrep -v '^($|%)' ``` is opbject-type specific
I'm not sure what you mean, exactly what you mean, but... The '-r' flag seems to disable related answers and is not type-specific. You can use the '-x' flag to prevent searching for less-specific matches, which is the default behavior. I believe this applies for all hierarchical types (so at least inet6num, route6, inetnum, route, as-block, and domain object types). You may want to still couple the '-x' with '-T', since you can end up with inetnum and route objects returned, or aut-num and as-block. Cheers, -- Shane
hi shane,
The '-r' flag seems to disable related answers and is not type-specific.
``` ran.psg.com:/home/randy> uname -a Linux ran.psg.com 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ran.psg.com:/home/randy> whois -h whois.ripe.net -r 147.28.0.0/16 % 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 '147.28.0.0 - 147.28.255.255' % Abuse contact for '147.28.0.0 - 147.28.255.255' is 'blackhole@bogus.com' inetnum: 147.28.0.0 - 147.28.255.255 netname: RG79-147-28 country: US org: ORG-RO47-RIPE admin-c: RB45695-RIPE tech-c: RB45695-RIPE status: LEGACY mnt-by: MAINT-RGNET mnt-domains: MAINT-RGNET mnt-routes: MAINT-RGNET mnt-by: RIPE-NCC-LEGACY-MNT created: 2016-03-16T15:16:35Z last-modified: 2019-08-08T01:21:04Z source: RIPE % Information related to '147.28.0.0/16AS3130' route: 147.28.0.0/16 descr: RGnet/PSGnet origin: AS3130 mnt-by: MAINT-RGNET created: 1970-01-01T00:00:00Z last-modified: 2003-12-22T01:59:14Z source: RIPE # Filtered % This query was served by the RIPE Database Query Service version 1.94.1 (ANGUS) ```
* Randy Bush via db-wg
ran.psg.com:/home/randy> whois -h whois.ripe.net -r 147.28.0.0/16
Perhaps your whois clients eats the «-r» parameter. Try «whois -h whois.ripe.net -- -r 147.28.0.0/16 instead»? Tore
On Tue, Aug 27, 2019 at 03:02:35PM +0200, Tore Anderson via db-wg wrote:
* Randy Bush via db-wg
ran.psg.com:/home/randy> whois -h whois.ripe.net -r 147.28.0.0/16
Perhaps your whois clients eats the ??-r?? parameter.
Try ??whois -h whois.ripe.net -- -r 147.28.0.0/16 instead???
It is not that case: -r turn off recursive look-ups for contact information And -r is the answer to Randy's question, since he was asking about "not also the org: person: and grandmother: objects". ;-) Piotr -- Piotr Strzyżewski Silesian University of Technology, Computer Centre Gliwice, Poland
* Tore Anderson via db-wg
Perhaps your whois clients eats the «-r» parameter.
Try «whois -h whois.ripe.net -- -r 147.28.0.0/16 instead»?
Uh, wait. The output you posted seems correct to me? You asked for 147.28.0.0/16 and got the expected exact match results, an inetnum and a route. No org/person/grandmothers were returned - so what was the problem, exactly? Tore
participants (4)
-
Piotr Strzyzewski -
Randy Bush -
Shane Kerr -
Tore Anderson