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/dns-wg@ripe.net/

[dns-wg] Analysis of NSD

Previous message (by thread): [dns-wg] Re: name servers with database back-ends
Next message (by thread): [dns-wg] Analysis of NSD

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Jim Reid jim at rfc1035.com
Wed Oct 27 13:16:07 CEST 2004

>>>>> "Stephane" == Stephane Bortzmeyer <bortzmeyer at nic.fr> writes:

    >> Well, for NSD, using large zones will cause it to eat memory
    >> exponentially.

    Stephane> Here is the NSD maintainer's analysis:

    Stephane> http://open.nlnetlabs.nl/pipermail/nsd-users/2004-October/000276.html

While there is no reason to dispute the analysis from NSD's authors, I
do think it would be nice if there was an independent analysis of NSD.
And other DNS implementations for that matter. The work Brad did a
couple of years ago was a step in that direction.

I would also encourage operators to share their experiences of
different name server implementations here: performance, protocol
compliance, features, management & support issues, SLAs with hosting
providers, etc, etc. Capturing and documenting this anecdotal
information would be very useful.

Previous message (by thread): [dns-wg] Re: name servers with database back-ends
Next message (by thread): [dns-wg] Analysis of NSD

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ dns-wg Archives ]