This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[db-wg] domain: object normalization
- Previous message (by thread): [db-wg] The release of RPSLng IRRToolSet
- Next message (by thread): [db-wg] domain: object normalization
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Pim van Pelt
pim at bit.nl
Fri Aug 6 11:33:38 CEST 2004
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 ? -- Met vriendelijke groet, BIT BV / Ing P.B. van Pelt PBVP1-RIPE (PGPKEY-4DCA7E5E)
- Previous message (by thread): [db-wg] The release of RPSLng IRRToolSet
- Next message (by thread): [db-wg] domain: object normalization
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]