Hi Jeroen! Jeroen Massar wrote: [...]
That trick works at the moment only when the object has a direct IRT object related to it.
In the v4-world it works as expected, e.g. 193.171.3.0 - 193.171.3.255 does NOT have a direct link to our irt object, but it gets returned as expected (by me :-) from the /16 (or /15?))
Take for instance 2001:7b8:300::/48 and it won't return it,
As the /40 has a link to the irt: I consider that behaviour a bug ;-)
unless you add the -c option. Which is prolly why you said '1st step' as that will be the 2nd step. But the 1st step has already been in place for quite some time afaik...
Actually the 2nd step was discussed as changing the default behaviour of the commandline interface, too. The general feeling was that most queries by the walk-in customers would be run through the web interface anyway, and the NCC was reluctant to immediately change the interface which is probably used by scripts and programs...
Btw, to everyone just reading along :-) This lookup interface is pretty cool as it does support including your favourity whois flags like -T, -r and friends in the lookup key entry-box!
IMHO the cool part is the "Advanced" box so that one can select the flags and construct a query, allowing me to forget all those options ;)
Greets, Jeroen
Wilfried