how to find what features/options added between releases?
Stacey Marshall
stacey.marshall at sun.com
Thu May 10 16:32:01 UTC 2007
Jeremy C. Reed wrote:
> I am trying to compile a list of the features and options added (and maybe
> removed or syntax changed) between the 9.2.x, 9.3.x, 9.4.x, and HEAD. (My
> list is below.)
>
> As of today the releases are:
> BIND 9.4.1 (current official release)
> BIND 9.3.4 (maintenance release)
> BIND 9.2.8 (maintenance release with end of life August 2007)
>
> I was told that the CVS tags for the release branches are v9_2, v9_3 and
> v9_4 (for 9.2.x, 9.3.x and 9.4.x).
>
> Comparing the Bv9ARM-book.xml for the different release branches doesn't
> seem good enough, as I am not sure if the features already existed but
> just not documented.
>
> For example, v9_4 documents notify-delay but v9_4_1 does not.
>
> Is comparing bin/named/config.c the best way?
>
> (For config.c, v9_3 is same as v9_3_4, v9_2 is same as v9_2_8, and v9_4 is
> same as v9_4_1 so that makes it easy.)
>
> Here is a start of my list. Please double-check this for me.
>
> New in 9.3:
>
> recursing-file
> server-id
> tcp-listen-queue
> edns-udp-size
> dnssec-enable
> alt-transfer-source
> alt-transfer-source-v6
> multi-master
> max-journal-size
> ixfr-from-differences
>
> Removed in 9.3:
>
> version
> allow-v6-synthesis
>
> New in 9.4:
>
> allow-query-cache
> check-mx
> acache-enable
> acache-cleaning-interval
> max-acache-size
> dnssec-enable yes
> dnssec-validation
> dnssec-accept-expired
> clients-per-query
> max-clients-per-query
> zero-no-soa-ttl-cache
> notify-delay
> check-wildcard
> check-sibling
> check-integrity
> check-mx-cname
> check-srv-cname
> zero-no-soa-ttl
> update-check-ksk
>
> New in 9.5
>
> allow-query-cache-on
> allow-recursion-on
> allow-query-on
> try-tcp-refresh
>
> Does a list like this already exist?
>
> Should I be looking at different source file?
>
> Jeremy C. Reed
>
> p.s. I am doing this because I want to help improve the reference manual
> so an admin will know when features are added. This will make it easier
> for an admin to use one reference manual for different systems and will
> make it easier to learn new features (such as using maintenance release
> and moving to current official release). Also I think this may make it
> easier for ISC developers so they won't have to keep numerous different
> versions of ARM (because maybe one ARM can be used for all if it is clear
> on the differences).
>
Hi Jeremy,
This would be very beneficial for integrating new releases in Solaris as
this information is expected for inception review. It would be really
fantastic if the migration.txt file within BIND CVS tree was maintained
with this information....
Here is what I documented between BIND 9.2 and 9.3:
IId. Differences in BIND 9.3 from BIND 9.2
-------------------------------------
BIND 9.3 provides several changes from BIND 9.2, including but
not limited to:
1. DNSSEC tools provided by BIND 9.2.4 are not compatible with BIND 9.3.4
and are replaced where applicable. Specifically, DNSSEC-bis
functionality removes the need for dnssec-signkey(1M) and
dnssec-makekeyset(1M); dnssec-keygen(1M) and dnssec-signzone(1M) now
provide alternative functionality.
2. dig(1M) and nslookup(1M) now report "Not Implemented" as NOTIMP rather
than NOTIMPL. This will have impact on scripts that are looking for
NOTIMPL.
3. named(1M): BIND server process includes new command line options to
overcome certain operating environment issues; CR 6320428. These
options are:
* '-4' specifies to only send queries on IPv4 interfaces
* '-6' specifies to only send queries on IPv6 interfaces.
named no longer provides the following functionality:
* Inverse IPv6 queries to the obsolete ip6.int domain. The
ip6.arpa domain is obsoleted by the ip6.int domain. See RFC
3596.
* IPv6 does not forward A6 lookups, deprecated by RFC 3363
* IPv6 "bitstring" not supported, primary will refuse to load zone
files with binary labels. Deprecated by rfc3363.
* Zones containing MD (Mail Destination) and MF (Mail Forwarder)
will now be rejected. The MD and MF resource record (RR) types
were originally introduced in RFC 882 and subsequently obsoleted
in RFC 1035 by the MX RR.
4. named.conf: Has additional options:
* allow-update-forwarding
* alt-transfer-source
* alt-transfer-source-v6
* avoid-v4-udp-ports
* avoid-v6-udp-ports
* check-names: Validate names in zones (from BIND 8).
* disable-algorithms
* dnssec-enable
* dnssec-lookaside
* dnssec-must-be-secure
* dual-stack-servers: provides IPv4/IPv6 transition support.
* edns-udp-size: Set advertised EDNS UDP size.
* flush-zones-on-shutdown
* hostname (chaos)'
* ixfr-from-differences: use IXFR deltas when loading master files.
* masters: define masters for a zone.
* max-journal-size: specify the size of a journal
* multi-master
* querylog
* server-id (chaos)
* Server statement grammar includes:
* transfer-source
* transfer-source-v6
* tcp-listen-queue
* use-alt-transfer-source
* zone statement grammar:
* multi-master
* key-directory
named.conf removed options:
* allow-v6-synthesis: Obsolete. Caused named to translate ip6.int
requests to ip6.arpa requests. As the ip6.int domain is now
obsolete this option has been removed.
* zone-statistics has been removed from the 'view' statement.
5. dig(1M) has new command line options, -4, -6, +[no]aaflag, +[no]cl,
+[no]ttlid, +tries=T and +retry=T
6. named.checkconf(1M) has new options:
-z: Perform a check load of the master zonefiles found in named.conf.
-j: When loading a zonefile read the journal if it exists.
7. named-checkzone(1M) has new options:
-k mode: Perform "check-name" checks with the specified failure mode.
-n mode: Check NS records are addresses, mode is warn, fail or ignore.
-o filename: Write zone output to filename.
-t directory: chroot to directory, useful for include statements.
-w directory: chdir to directory, useful for include statements.
-D: Dump zone file in canonical format.
8. rndc(1M) has several new subcommands including:
freeze, thaw, flushname and recursing (see above).
Several subcommands have new options namely stop, halt and dumpdb.
9. (1M) generates SIG(0) signed messages.
I attached the migration.txt document (where the above was extracted
from) which we provide with Solaris BIND distribution.
Stace
--
Stacey Jonathan Marshall.
Solaris Revenue Product Engineering, EMEA
Sun Microsystems Limited. +44-(0)1252-426106 (x26106)
---------------------------------------------------------------------
http://blogs.sun.com/ace
---------------------------------------------------------------------
NOTICE: This email message is for the sole use of the intended
recipient(s) and may contain confidential and privileged
information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact
the sender by reply email and destroy all copies of the original
message.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: migration.txt
URL: <https://lists.isc.org/pipermail/bind-workers/attachments/20070510/41d496fc/attachment.txt>
More information about the bind-workers
mailing list