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/db-wg@ripe.net/
[db-wg] Verio renamed NTTCOM in RIPE Database
- Previous message (by thread): [db-wg] Verio renamed NTTCOM in RIPE Database
- Next message (by thread): [db-wg] Verio renamed NTTCOM in RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ruediger Volk, Deutsche Telekom T-Com - TE141-P1
rv at nic.dtag.de
Wed May 30 22:50:14 CEST 2007
> > On 31 March 2007, the Verio routing registry database was renamed > > NTTCOM. This change of name has been incorporated in the RIPE Database > > server which mirrors a number of public databases including the NTTCOM > > routing registry. > > > > More information about the NTTCOM routing registry is available at: > > http://www.us.ntt.net/about/policy/rr.cfm > > how/when will that affect us poor peval() users? > > `/usr/local/bin/peval -s $IRR $OBJ > > do we just change $IRR from VERIO to NTTCOM and it will all work? yes Assuming that defaults/environment/additional flags in appropriate position for the database host and access protocol (radb ./. ripe) are right that should do it - and I can report success using peval/RtConfig derivatives for a couple of days. > randy Cheers, Ruediger
- Previous message (by thread): [db-wg] Verio renamed NTTCOM in RIPE Database
- Next message (by thread): [db-wg] Verio renamed NTTCOM in RIPE Database
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]