Hi Fredrik, just to make sure that the behaviour - and thus the problem - is: when inverse searching for that notify: attribute value, the whois software does pick up the inetnum:, due to the notify: attribute in the maintainer, but not the route:, although it is equally covered by that same maintainer. Correct? If that's the case then I guess you stumbled over bug (or weird interaction or side-effect of using an object type list :-) ) Regards, Wilfried. Fredrik Widell wrote:
Hello db-wg.
I would like to change the behaviour of the whois-output for the following query
whois -h whois.ripe.net -- "-r -T inetnum,route -i notify info@resilans.se"
Via that question, I will see every object that has the notify info@resilans.se set, which right now is
inetnum: 194.14.3.0 - 194.14.3.255 netname: RESILANS descr: Resilans AB remarks: VV org: ORG-ABUS1000-RIPE country: SE admin-c: RESI1-RIPE tech-c: RESI1-RIPE status: ASSIGNED PI mnt-by: RESILANS-MNT mnt-domains: RESILANS-MNT mnt-routes: RESILANS-MNT source: RIPE # Filtered
However, my request is that the above query should give the exact same output as the below query
whois -h whois.ripe.net -- "-r -T inetnum,route 194.14.3.0"
which will also display the corresponding route-object, is there any real reason why this is not displayed with an inverse query? it looks like:
inetnum: 194.14.3.0 - 194.14.3.255 netname: RESILANS descr: Resilans AB remarks: VV org: ORG-ABUS1000-RIPE country: SE admin-c: RESI1-RIPE tech-c: RESI1-RIPE status: ASSIGNED PI mnt-by: RESILANS-MNT mnt-domains: RESILANS-MNT mnt-routes: RESILANS-MNT source: RIPE # Filtered
route: 194.14.3.0/24 descr: Resilans AB origin: AS12381 mnt-by: RESILANS-MNT source: RIPE # Filtered