nsd users - Jul 2012 - NSD 3.2.11 with TLSA and ECDSA

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

There is a new release for nsd: 3.2.11. It is available here:

www:  http://nlnetlabs.nl/downloads/nsd/nsd-3.2.11.tar.gz
sha1: 4b8b9293fd13b0fba2a2bff9fd11940e0d8d7448

This release has some features, and some bug fixes too. This version
of nsd understands new DNSKEY algorithm mnemonics, including GOST and
ECDSA, as well as the TLSA RRtype (for DANE support). You can enable
'per zone statistics', with --enable-zone-stats. For more information,
see the RELNOTES below.

Best regards,
  Matthijs


NSD 3.2.11 RELEASE NOTES:

FEATURES:
- - Fallback to AXFR if IXFR is unknown at the primary. NSD considers
  IXFR unknown at the primary if there is a negative response for the
  IXFR RRtype. This does not override the value for
  'allow-axfr-fallback'.
- - Allow for reading in new DNSKEY algorithm mnemonics (RFC5155,
  RFC5702, RFC5933, and RFC6605 (ECDSA)).
- - Zone statistics, enable with --enable-zone-stats. This stores the
  BIND8 stats per zone in a configurable statistics file. This option
  does not scale and should therefore not be enabled when serving
  many zones.
- - Support for TLSA RRtype (DANE).

BUG FIXES:
- - Fix for qtype ANY for a wildcard domain in NSEC signed zone: Don't
  add the wildcard domain NSEC into the answer section. Instead,
  put the wildcard expanded NSEC into the answer section and keep the
  wildcard domain NSEC in the authority section.
- - Fix for accept spinning reported by OpenBSD.
- - Fix restart failed due to bad ixfr packet because of zone removed
  from nsd.conf.
- - Bugfix #453: typo in nsdc man page.

OPERATIONAL NOTES:
- - NSD uses the query name for dname compression again (Fix #235
  had as side effect that this didn't happen anymore and is hereby
  undone).

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJP+qRxAAoJEA8yVCPsQCW5yLoIAMyQUS8cgSZphBCgSFKfqBYj
Qb1l3D9/PoaLI/uplwtow9t1fWbMBgXkYM+v+N9MsIO79vObCcHwftg/+s5jrYBz
puuKr24ff+I9FQj0fFQiZv6zrEmP2+lGqlNigF9QkDNfObsJVDCQjFYX0lgkcnYy
DuGqE69mlmmee19iW0m0PRo5/shNuMdK77xP958MOQTRQwhKXVDN4BK2YQp0LN/W
0R2gn6ZqfuWUYZ84EdbUTyT5A9p7wxwv4zwg3Zgndw87U9DePY7RB20PA+s4KBxZ
/RKhmXEg/ImWmucRfwvXx8k/xD21NYKhVViLpVqam6UHQTHyYRXp1IfO9NTX8I0=uU6k
-----END PGP SIGNATURE-----

On Mon, Jul 09, 2012 at 11:29:21AM +0200,
 Matthijs Mekking <matthijs at NLnetLabs.nl> wrote 
 a message of 66 lines which said:
> - - Allow for reading in new DNSKEY algorithm mnemonics (RFC5155,
>   RFC5702, RFC5933, and RFC6605 (ECDSA)).
I'm confused. Does it mean it can serve a zone signed with GOST or
ECDSA? Or just that it can load a zone with GOST or ECDSA DNSKEYs?