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] --list-versions
- Previous message (by thread): [db-wg] --list-versions
- Next message (by thread): [db-wg] --list-versions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ronald F. Guilmette
rfg at tristatelogic.com
Tue Jun 25 20:47:11 CEST 2019
In message <90575aee-1245-9de6-86ac-417c3614d12c at fud.no>, Tore Anderson <tore at fud.no> wrote: >* Ronald F. Guilmette via db-wg >> --list-versions 194.162.0.0 >> --list-versions DE-ECOTEL-950515 >> >> I am having serious trouble understanding why this isn't working. >> >> If someone could explain, I'd appreciate it. > >a) Use an unambiguous primary/lookup key, e.g.: > >$ whois -h whois.ripe.net -- --list-versions 194.162.0.0/16 Ahhhhhhh! Thank you! This is the magic I was missing. And it makes perfect sense, now that you say it. >b) «netname objects» don't exist, so no, not supposed to work. That comment makes no sense however. Those objects -do- exist in the data base and a normal WHOIS query finds them. So I'm really still not clear on why I can't apply --list-versions and --show-version to them. Regards, rfg
- Previous message (by thread): [db-wg] --list-versions
- Next message (by thread): [db-wg] --list-versions
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]