NSD now includes an AXFR client (nsd-xfer) as a replacement for bind 8's
named-xfer, as well as various bug fixes and internal changes.
Thanks to Stephane Bortzmeyer for helping to test this release and
improve the OpenSSL detection in the configuration script.
Please see the README document for configuration and installation
instructions.
You can download NSD from http://www.nlnetlabs.nl/nsd/
NSD 2.2.0 release notes:
FEATURES:
- nsd-xfer: replacement program for named-xfer to perform zone
transfers using AXFR. TSIG is supported by nsd-xfer but not
yet by the nsd server. DNSSEC is also supported. TSIG
requires OpenSSL version 0.9.7 or higher, configure using
--disable-tsig if you do not have OpenSSL installed.
Configure using --with-ssl=path if OpenSSL is not installed
at a standard location.
CODE CHANGES:
- New data structure 'buffer_type' for representing binary
buffers that can be read, written, and resized. Data in
these buffers is stored in network byte order. This data
structure replaces the iobuf field of 'struct query'.
BUG FIXES:
- Fixed endian problem in WKS record.
- Protocol can now be specified numerically in WKS record.
- Allow escape sequences (\DDD) in TTL, RR class, and RR type.
- The zone compiler now accepts many more characters in
unquoted strings such as domain name labels. The characters
no longer need to be escaped with a backslash.
- Close included files after reading.
- Maximum TCP message size is now 65535 bytes. AXFR response
packets are still limited to 16383 bytes for optimal
compression of dnames.
- The TSIG key for AXFRs can now also be stored in the file
<zonename>.tsiginfo. This makes it possible to use TSIG
with multiple master servers.
- Signals are no longer blocked while performing I/O so the
server should respond quicker to signals.
- Fixed parsing of LOC rdata. Fractions and altitude were not
handled correctly.
On Tue, 18 Jan 2005 15:35:49 +0100 Erik Rozendaal <erik at NLnetLabs.nl> wrote: :NSD now includes an AXFR client (nsd-xfer) as a replacement for bind 8's :named-xfer, as well as various bug fixes and internal changes. : If a zone transfer fails, it doesn't tell you which zone failed (Failure is mostly expected, as that master is having some network problems). nsd-xfer: failed to read response size: Connection timed out Other than that, its working fine for me on OpenBSD -current/macppc. -- The church is near but the road is icy; the bar is far away but I will walk carefully. -- Russian Proverb
On Tue, Jan 18, 2005 at 03:35:49PM +0100, Erik Rozendaal <erik at NLnetLabs.nl> wrote a message of 53 lines which said:> NSD now includes an AXFR client (nsd-xfer) as a replacement for bind > 8's named-xfer, as well as various bug fixes and internal changes.NSD 2.2 is now running on {ns2,b}.nic.fr. Thanks to everyone, nsd-xfer is a big improvment. Also, we are now able to serve broken zones like ".ge" (TTL does not match the TTL of the RRset). When you are secondary for hundreds of domains, it help. This is probably the last version of NSD that will run on Alpha/Tru64, the machine will soon be replaced, probably by a PC/Opteron/Debian/GNU/Linux.