This release is a bug fix release.
Please read the README document for configuration and installation
instructions.
You can download NSD from http://www.nlnetlabs.nl/nsd/
NSD 1.2.1 release notes:
BUG FIXES:
- AXFR terminates early if a zone containa a CNAME pointing
the the zone's domain name (SOA record) (bug #56).
- During an AXFR memory above the top of the stack was
accessed. This could lead to occassional AXFR errors (bad
packets).
- NSD now prints its version number and exits when invoked
with the -v flag (bug #57).
- NSD prints help information and exits when invoked with the
-h flag.
This release is a bug fix release.
Are there plans to make another bug-fix release for bugzilla bugs 59 and
60 in the short term, or are you planning a cooling-off period?
Nick
Nick Hilliard wrote:
This release is a bug fix release.
Are there plans to make another bug-fix release for bugzilla bugs 59 and
60 in the short term, or are you planning a cooling-off period?
There will probably be a 1.2.2 release early next week to fix these two bugs. So if anyone is holding on to any other bugs, please send them in so they can be fixed ASAP 
Erik
Nick Hilliard wrote:
>>This release is a bug fix release.
>
>
> Are there plans to make another bug-fix release for bugzilla bugs 59 and
> 60 in the short term, or are you planning a cooling-off period?
There will probably be a 1.2.2 release early next week to fix these two
bugs. So if anyone is holding on to any other bugs, please send them in so
they can be fixed ASAP
There is bug on Linux:
IPv6 enabled daemon doesn't run on non IPv6 enabled kernel, in syslog
reports:
nsd[551]: can't create a socket: Address family not supported by
protocol
I made workaround in startup script to add -4 when /proc/sys/net/ipv6/
directory doesn't exist in debian package, but this is really only
workaround, not fix.
from discussion with Colm MacCarthaigh:
> Will you fix it soon?
It's not so easily doable. The problem is that getaddrinfo
is returning :: when it really should return 0.0.0.0, getaddrinfo
doesnt seem to pay any attention to whether IPv6 is configured
or not.
The only way to get around this problem would be to try to bind
to :: and if that fails, bind to 0.0.0.0 , but that causes other
problems for IPv6 users.
Code would have to be added to NSD to detect whether the system
had IPv6 configured or not 
This is probably better left to
init scripts.
O.