[db-wg] domain: object normalization

On 2004-08-06 11:33:38 +0200, Pim van Pelt wrote:
> Hi,
> 
> I keep on bumping into something with the RIPE database. I'm used to
> the pedantic trailing dot in hostnames, such as 'www.bit.nl.'; I
> also always write domains like so: '122.109.193.in-addr.arpa.'.
> 
> $ whois -h whois.ripe.net 122.109.193.in-addr.arpa.
> % This is the RIPE Whois server.
> % The objects are in RPSL format.
> %
> % Rights restricted by copyright.
> % See http://www.ripe.net/ripencc/pub-services/db/copyright.html
> 
> %ERROR:101: no entries found
> %
> % No entries found in the selected source(s).
> 
> Without the trailing dot, this works just fine. Is it feasable to
> have the scanner normalize the hostname/domain into something that
> your backend can look up ? 

Sure, this is straightforward.  We do this for IP lookups now, for
instance:

%WARNING:905: fixed lookup key
%
% The key "193.0.1" has been changed to "193.0.1.0" for lookup.

The server will return a similar warning for these cases:

%WARNING:905: fixed lookup key
%
% The key "122.109.193.in-addr.arpa." has been changed to "122.109.193.in-addr.arpa" for lookup.

-- 
Shane Kerr
RIPE NCC