Ripe change to whois

Hank Nussbacher wrote:
> Just check http://www.checkdomain.com with some nonexistant domain housed at
> RIPE and tell me if something isn't wrong here.  -Hank

Something is wrong but I don't think it's the RIPE db.  If a third party
writes an application which doesn't correctly parse the information it
receives from the RIPE database then I don't see how this can be the fault
of either the RIPE NCC or those participating in the development of the
database.

Returning the next object up in the hierarchy seems sensible behaviour. It's
certainly what I become used to when querying for inetnum or route objects -
when normally I just paste an "interesting" host IP address into my whois
query and expect to get back the details of the allocation/assignment
containing that host address.

Perhaps, in the same way that the RIPE db supports the -L, -m and -M flags
(at least where inetnum and route objects are concerned), there should be an
option for the database to only return an exact match.

[      -L find all Less specific matches
       -m find first level More specific matches
       -M find all More specific matches		]

James

----- ___                       - James Aldridge, Senior Network Engineer,
---- /    /   /  ___  ____ _/_ -- EUnet Communications Services BV
--- /--- /   / /   / /___/ /  --- Singel 540, 1017 AZ Amsterdam, NL
-- /___ /___/ /   / /___  /_ ---- Tel: +31 20 530 5327; Fax: +31 20 622 4657
-                           ----- 24hr emergency number: +31 20 421 0865