Hosting many domains as a secondary: parallelizing "nsdc update"

Wouter Wijngaards wouter at
Tue Jul 25 13:28:24 UTC 2006

Hash: SHA1

Stephane Bortzmeyer wrote:
> On Fri, Jul 07, 2006 at 11:12:26AM +0200,
>  Stephane Bortzmeyer <bortzmeyer at> wrote 
>  a message of 214 lines which said:
>> Therefore, I suggest the following solution:
> Implemented today, we'll see if our Russian or Dutch colleagues scream
> :-)
>> Advices? 
> Here is the suggested patch against nsd 2.3.5. We would like to see it
> integrated.

Hi Stephane,

Thanks for the bugreports and the patch. Excellent stuff; I have
incorporated bugfixes for the locking bugs you found and the patch is
added to the nsd contrib folder (I have adapted to patch to work with
the current svn, and added a small readme/howto for it). This will be in
the next point release.

I did not incorporate the patch into the mainline NSD 2.x code. Partly
because it is a complicating feature, but mostly because with the
upcoming NSD 3 you can get the same functionality with its AXFR/IXFR

NSD3 can perform AXFR / IXFR transfer requests in parallel out of the
box. Currently it is '-j 10' (tweaked with the XFRD_MAX_TCP constant).
NSD3 does not use gnu make for that, it starts a separate process for
the transfers, that sleeps in a select() statement for most of the time.
At a timeout or a notify message it will wake up and perform a zone
transfer for the zone (with IXFR and TSIG support). So it has only one
process that does all the transfers.

The new feature keeps track of the time as well, so that zones are
refreshed according the times from the SOA record. You can send notify
messages to the server to force zone updates.

NSD 3 is in testing now, you can get it from the subversion repository
if you are interested.

Best regards,
Version: GnuPG v1.4.4 (GNU/Linux)
Comment: Using GnuPG with Fedora -


More information about the nsd-users mailing list