Release of NSD 3.0.5

NSD
1

Hi,

NSD 3.0.5 is available at:
http://www.nlnetlabs.nl/downloads/nsd/nsd-3.0.5.tar.gz
  with SHA-1:
e6b433e0017d51b8c3f31897053d6c7718957627

Please note:
o Fixes bug where NSD would stall during reload. The bug resulted in
secondary zones not being updated.
This bug was introduced in NSD 3.0.3 as part of a bugfix to prevent
possible loss of incoming NOTIFYs during a reload.
o verbosity setting (-V, nsd.conf) to see what is happening.
o zonesdir default setting is /etc/nsd. If you have not done so already,
please override the 'zonesdir:' setting in your nsd.conf.
Previously the default was "" to use to current working directory, which
is confusing for daemon commands run from shell scripts.

The release notes are:
BUG FIXES:
* Fixed problem with reload waiting very long. If the OS has a
  raging herd problem, NSD could block in a UDP operation and
  that process would stop reload from finishing. Made UDP sockets
  nonblocking.
* Made TCP listen sockets nonblocking. NSD could block in accept.
* Handle the new CERT RDATA types defined in RFC 4398 (submitted by
  Mans Nilsson).
* Fixed a bug where zonec would choke on unknown CERT RDATA types.
* Change nsd-notify retry timer from linear into exponential
  backoff (submitted by Mans Nilsson).
* Debug flag (-d) behavior changed. Nsd now also forks children when
  run in debug mode.
* Added verbosity mode (-V <level>) for extra operational logging.
* zonesdir default is /etc/nsd. This can be overridden in nsd.conf.
* if clients drop the tcp connection this does not result in a logfile
  entry, unless verbosity is set 2 or more.

Best regards,
   Wouter

2

On our name server, it does not go too far. It loads the database,
then logs:

[1175075157] nsd[2287]: error: malloc failed: Cannot allocate memory

and dies.

3

Stephane Bortzmeyer wrote:

On our name server, it does not go too far. It loads the database,
then logs:

[1175075157] nsd[2287]: error: malloc failed: Cannot allocate memory

and dies.

There have not been any changes to memory allocation in the 3.0.5
release. No extra memory is used. This is a surprising error.

Could you send me more details on your memory setup (off list) ?

Best regards,
   Wouter