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] RIPE DB tertiary whois server
- Previous message (by thread): [db-wg] RIPE DB tertiary whois server
- Next message (by thread): [db-wg] Alex Dempsey/Vodafone is out of the office.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Engin Gunduz
engin at ripe.net
Tue Nov 9 01:56:34 CET 2004
Hi, We will send a more detailed report when the work moves forward a little more, but: We have been testing new faster hardware that will replace the current whois server hardware. That 'tertiary' server is one of the new boxes. We called it tertiary for the moment but it (and its sisters) will replace the old slow hardware totally later. The work consists of changing the hardware as well as the OS (the old hardware runs Solaris, the new ones will be Linux). Regards, -engin On 2004-11-09 00:47:09 +0100, Daniel Roesen wrote: > On Tue, Nov 09, 2004 at 12:38:53AM +0100, Sascha Lenz wrote: > > My main concern wasn't the query-speed but the update-speed though. > > I mean, when i supplied an update via auto-dbm i got instant replies, > > but the change took about 24 hours or longer to be reflected in the > > whois query again. > > We just had reports that currently DB updates are reflected virtually > instantly in the whois server. > > > Regards, > Daniel > > -- > CLUE-RIPE -- Jabber: dr at cluenet.de -- dr at IRCnet -- PGP: 0xA85C8AA0 -- Engin Gunduz RIPE NCC Software Engineering Department
- Previous message (by thread): [db-wg] RIPE DB tertiary whois server
- Next message (by thread): [db-wg] Alex Dempsey/Vodafone is out of the office.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]