adns 1.5.0~rc1
Ian Jackson
ijackson at chiark.greenend.org.uk
Sun Oct 26 13:31:47 GMT 2014
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
I am pleased to announce the availability of adns 1.5.0~rc1, the
second release candidate of adns 1.5.0.
Changes in adns 1.5.0, since adns 1.4, are:
New features:
* This release provides full IPv6 support. Applications can request
AAAA records (containing IPv6 addresses) as well as, or instead of,
A records (containing IPv4 addresses). adns 1.5 can speak to
nameservers over IPv6.
* adns_addr2text and adns_text2addr: Convenient C functions for
converting between addresses and address literals. These carry
less baggage than getaddrinfo and getnameinfo.
Bugfixes:
* We fix a crashing bug in adnslogres. (Debian#392102.)
* Previously, parsing of some adns_specific options in resolv.conf
would go awry if multiple options were specified on the same line.
(Fixed since 1.5.0~rc0.)
* adns now knows to ignore more things in resolv.conf, rather than
warn about them, and there's also an option to disable all of these
warnings. (Debian#411263.) (Fixed since 1.5.0~rc0.)
* Previously, some harmless but wrong owner names for checked ptr
queries would be accepted; now they are rejected with `Domain
invalid for particular DNS query type'.
Other:
* There are some minor API/ABI changes and improvements, for future
proofing.
* There are also some build system, test suite and coding style
improvements.
* Licence is now GPLv3.
Compatibility:
adns 1.5 is fully forwards API- and ABI-compatible with 1.4.
adns 1.5 is not backwards ABI-compatible, in the sense that
applications built against adns 1.5 but run with adns 1.4 may
experience `Function not implemented' errors, or `symbol lookup
error' due to undefined symbols. But applications built against 1.4
will not experience data corruption due to ABI mismatches.
adns_r_addr queries (general `address' queries where the application
does not specify the kind of address) used to only return AF_INET
(IPv4) addresses. To avoid surprising existing applications,
AF_INET6 (IPv6) addresses will be returned only if the application
explicitly states its support for handling a mixture of address
families in the results from adns_r_addr. In a future version of
adns this will become the default.
adnshost and the other command-line utilities are fully forward- and
backward-compatible, except that in adns 1.5, adnshost will return
IPv6 as well as IPv4 information if simply asked for `addresses'.
Calling programs which did not ask for a specific address type ought
to cope with this.
The API in 1.5.0 also fixes a technical nonconformance to the C
specification. On platforms where an `enum' type might be an
integer type whose size is bits is not a power of two, there could
be an incompatible ABI change between 1.4 and 1.5 - but we don't
think there are many (if any) such platforms which are sufficiently
POSIX-like for adns. (Changed since 1.5.0~rc0.)
Please note the new bug reporting arrangements, documented in
README.html in the source tree.
The files are available here:
http://www.chiark.greenend.org.uk/~ian/adns/ftp/
Here are the SHA-256 checksums:
c0436fd14cf9a3708b252898028d5d4b2c246e177018738b6e1337312c03c3c1 adns-1.5.0~rc1.tar.gz
ff610a93f391c3b17cd062bdacb47a1c2fc175688da37f24d5e7b5ee7afee2ee adns-1.5.0~rc1.tar.gz.sig
There is no diff provided between 1.4 and 1.5.0~rc1. The changes
(mostly for IPv6 support) are extensive.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQEcBAEBCAAGBQJUTPedAAoJEOPjOSNItQ05snAH/iilFIb+uR5DYN4Wlljie2GR
AeTM+naddgTjYf3vtPdxgpo61DTfNtrHnGcAL3eUhwc2sB15lzO6fx4auRQHXZmf
W6JdyS4pfQdN3TlIA+ndBCv7La/eGJcEH4L1wL1P2fRN1HUYiZj+Km5rMR4pmtS9
N1PA/QhVWoZ5WrgNPsPERHciy9FSvRLS7wz6J0jbB3+MzSNvqEl855gT56fHV6oi
7W9f6BPje5j9tPqo6DHTA2Zn4N3gID1WQHVDK0B4zfTztzFjjkOR7HLTrbBJlf4m
U5ze6NX+CWfb4MzUcAjXrIVUaBBbkYo5d4AJXRgxfWWmhKZpsoAcSqCJVcXjCIM=
=LqBm
-----END PGP SIGNATURE-----
More information about the adns-announce
mailing list