pkgsrc/net/nsd/MESSAGE

28 lines
1.2 KiB
Text
Raw Normal View History

===========================================================================
$NetBSD: MESSAGE,v 1.4 2013/10/29 15:13:34 pettai Exp $
NSD 3.2.10 Bugfixes: * Bugfix #421: Truncate pidfile on shutdown, before unlink. * Bugfix #423: Fix slow zone transfer processing due to 'Fix is_existing flag for ENT' bugfix. * Bugfix #430: Fix segfault when MAX_INTERFACES set to more than 65K. * Fix configure.ac strptime check for gcc 4.6.2, acx_nlnetlabs.m4 update NSD 3.2.9 Features: * Minimize responses to reduce truncation: NSD will only add optional records to the authority and additional sections when the response size does not exceed the minimal response size. * The minimal response size is 512 (no-EDNS), 1480 (EDNS/IPv4), 1220 (EDNS/IPv6), or the advertized EDNS buffer size if that is smaller than the EDNS default. * The feature is enabled by default. You can disable it by configuring NSD with --disable-minimal-responses. * Less NSEC3 prehashing. This will make NSD handle zone transfers faster, but will decrease the performance of NXDOMAIN and wildcard NODATA responses. Full prehashing is enabled by default. If you want less NSEC3 prehashing, configure NSD with --disable-full-prehash. Thanks Secure64 for the patch. Bugfixes: * Bugfix #302: nsd accepts XFR but refuses to re-read the slave zone. * Bugfix #365: set patch style and zonec verbose for nsdc. * First step of bug #369: RRSIG DNSKEY sets zone to be treated DNSSEC. * Bugfix #375: typos in nsd.conf.5. * Bugfix #381: Binary escaped and transfers. * Bugfix #397: Don't allow relative domain names as origin in $INCLUDE directives. * Fix printout of IPSECKEY by nsd-patch. * Fix is_existing flag for ENT when domain that has a shared ENT is deleted by IXFR. (ENT == Empty Non-Terminal) * Fix bug if the zonefile is changed for a secondary but stored transfers are applied, and stop it from applying ixfr to empty zone. The zone is flagged with error and AXFR-ed. * Fix to have no authority NS set processing for CNAMEs. * Fix nsd-checkconf to check tsig algorithms properly. * Set the AA bit on responses that have an authoritative CNAME. * Fix denial of existence response for empty non-terminal that looks like a NSEC3-only domain (but has data below it). Operational notes: nsd.db version number increased because NSD 3.2.7 and earlier zonec is not compatible due to the TXT strings change. Please run nsdc rebuild before running NSD 3.2.9 and later versions.
2012-04-18 12:39:43 +02:00
The old NSD3 config file can be used without changes for NSD4. There are
new config statements and some old statements are gone.
The nsd.db file has a new format that allows read and write. Thus the
nsd.db file needs to be re-created in NSD4 format. This happens when
you start NSD4. NSD4 needs write permission on the nsd.db directory
for that. If you need to rollback to NSD3, run its zonec to recreate
the NSD3 nsd.db file (use nsdc rebuild).
The cron job for nsdc patch is no longer needed. It can be removed.
If you admire cron jobs, you can have a cron job that does "nsd-control
write". This would periodically write the contents of changed zones to
their zonefile.
nsdc is removed, reload with kill -HUP $pid and use nsd-control.
The SIGHUP makes NSD4 check zone file timestamps and reload changed zones.
nsd-control reload is the same. SIGTERM stops NSD.
You probably want to install and enable some of the new NSD 4 features,
such as set up nsd-control and statistics. And you may want to use the
new pattern config options.
===========================================================================