Hi, whatever this server is... can you please keep this one in production and not switch back to primary/secondary? :-) Wow, this one is really fast... Regards, Daniel -- CLUE-RIPE -- Jabber: dr@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0
Hay, Daniel Roesen wrote:
Hi,
whatever this server is... can you please keep this one in production and not switch back to primary/secondary? :-)
Wow, this one is really fast...
hehe % This is the RIPE Whois tertiary server. right, it certainly answers faster than the one active throughout the last days ... 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. I wrote a note to ripe-dbm but no reply up to now. Since I haven't seen any other (public) complaints or so here and no updates were lost, I didn't pursue this issue further. ...seems to be way better now, any comments on the problems or the new(?) tertiary server now from RIPE? :-) -- ======================================================================== = Sascha 'master' Lenz SLZ-RIPE slz@baycix.de = = NOC BayCIX GmbH = = http://www.noc.baycix.de/ * PGP public Key on demand * = ========================================================================
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@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0
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@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0
-- Engin Gunduz RIPE NCC Software Engineering Department
participants (3)
-
Daniel Roesen -
Engin Gunduz -
Sascha Lenz