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] Wierd output of whois/database
- Previous message (by thread): [db-wg] Wierd output of whois/database
- Next message (by thread): [db-wg] whois/database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Matthew Smith
m at mlnet.net
Wed Jul 13 19:44:21 CEST 2005
Shane, Thanks for your quick response, I thought it would be something I was doing wrong ;-) Regards Matthew Shane Kerr wrote: > Matthew, > > Matthew Smith wrote: > > >>if this is the wrong list, then please point me in the right >>direction. I am first assuming that I have done something wrong. >> >>I should have a role 'AHM' with two person objects (MS33051-RIPE and DB). >> >>The whois output (below) also gives two further records at the end >>which I cannot fathom how or why they appear. > > > The reason you are getting the SAR32-RIPE and SAR33-RIPE objects is > because the middle name of the person in these is "AHM", which is what > you were querying for. > > In your case, you can eliminate these two objects by asking for only > ROLE objects using the "-T" flag: > > $ whois -h whois.ripe.net -B -Trole AHM > > If there was a role object that had AHM in the name, then this would > appear, even with the type flag, so this will not work for any time > where you get "unwanted" objects back from your query. > > You might also be confused because the informational comment is wrong > for one of the person objects. This is a known bug that we hope to fix > shortly. > > -- > Shane > >
- Previous message (by thread): [db-wg] Wierd output of whois/database
- Next message (by thread): [db-wg] whois/database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]