a few problems with nsd 3.0.3

Wouter Wijngaards wouter at NLnetLabs.nl
Thu Dec 14 14:40:05 UTC 2006

Hash: SHA1

Hi Peter,

Hmm The large number of zones causes the processing time.

Can you provide more information?
* What are you doing? Starting it with no information? With preloaded
zone files? Doing a zone transfer?
* The zone files and config you used. :)
* You could compile with ./configure --enable-checking, start nsd -L 1
this will provide much more debug messages in the log; what it is using
the cpu for.

Send those to me directly; they are likely to be very large.

Right now I think it may be because the large number of zones is driving
a lot of interprocess data traffic or some slowness in the
zonetransfer-process. More information will tell.

Best regards,

Peter Larsen wrote:
> it seems like nsd locks up with 100% cpu load
> it looks like it loops with a gettimeofday lookup?
> it should be fair to say that i have loaded over 100000 zones in nsd  
> (yeah, im not normal :P)
> we get this in traces:
> gettimeofday({1166093621 109031},0x0)            = 0 (0x0)
> gettimeofday({1166093621 149335},0x0)            = 0 (0x0)

> system is freebsd 6.1 release
> nsd is from ports, 3.0.3
> regards, Peter - Larsen Data
> _______________________________________________
> nsd-users mailing list
> nsd-users at NLnetLabs.nl
> http://open.nlnetlabs.nl/mailman/listinfo/nsd-users

Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org


More information about the nsd-users mailing list