~mdw / adns / blame
| Commit | Line | Data |
|---|---|---|
| 6d88f2ba IJ |
1 | Changes in adns 1.5.1, since adns 1.5.0, are: |
| 2 | ||
| 3 | Bugfixes. See changelog. | |
| 4 | ||
| adaee51c IJ |
5 | Changes in adns 1.5.0, since adns 1.4, are: |
| 6 | ||
| 7 | New features: | |
| bcebe7fe IJ |
8 | |
| 9 | * This release provides full IPv6 support. Applications can request | |
| 10 | AAAA records (containing IPv6 addresses) as well as, or instead of, | |
| 11 | A records (containing IPv4 addresses). adns 1.5 can speak to | |
| 12 | nameservers over IPv6. | |
| 13 | ||
| adaee51c IJ |
14 | * adns_addr2text and adns_text2addr: Convenient C functions for |
| 15 | converting between addresses and address literals. These carry | |
| 16 | less baggage than getaddrinfo and getnameinfo. | |
| 17 | ||
| 18 | Bugfixes: | |
| 19 | ||
| 20 | * We fix a crashing bug in adnslogres. (Debian#392102.) | |
| 21 | ||
| 22 | * Previously, parsing of some adns_specific options in resolv.conf | |
| 23 | would go awry if multiple options were specified on the same line. | |
| 24 | (Fixed since 1.5.0~rc0.) | |
| 2065d373 | 25 | |
| adaee51c IJ |
26 | * adns now knows to ignore more things in resolv.conf, rather than |
| 27 | warn about them, and there's also an option to disable all of these | |
| 28 | warnings. (Debian#411263.) (Fixed since 1.5.0~rc0.) | |
| 29 | ||
| 30 | * Previously, some harmless but wrong owner names for checked ptr | |
| bcebe7fe IJ |
31 | queries would be accepted; now they are rejected with `Domain |
| 32 | invalid for particular DNS query type'. | |
| 33 | ||
| adaee51c IJ |
34 | Other: |
| 35 | ||
| 36 | * There are some minor API/ABI changes and improvements, for future | |
| 37 | proofing. | |
| bcebe7fe | 38 | |
| adaee51c IJ |
39 | * There are also some build system, test suite and coding style |
| 40 | improvements. | |
| bcebe7fe | 41 | |
| 23111d27 | 42 | * Licence is now GPLv3+. |
| 2065d373 | 43 | |
| bcebe7fe IJ |
44 | Compatibility: |
| 45 | ||
| 46 | adns 1.5 is fully forwards API- and ABI-compatible with 1.4. | |
| 47 | ||
| 48 | adns 1.5 is not backwards ABI-compatible, in the sense that | |
| 49 | applications built against adns 1.5 but run with adns 1.4 may | |
| 50 | experience `Function not implemented' errors, or `symbol lookup | |
| 51 | error' due to undefined symbols. But applications built against 1.4 | |
| 52 | will not experience data corruption due to ABI mismatches. | |
| 53 | ||
| 54 | adns_r_addr queries (general `address' queries where the application | |
| 55 | does not specify the kind of address) used to only return AF_INET | |
| 56 | (IPv4) addresses. To avoid surprising existing applications, | |
| 57 | AF_INET6 (IPv6) addresses will be returned only if the application | |
| 58 | explicitly states its support for handling a mixture of address | |
| 59 | families in the results from adns_r_addr. In a future version of | |
| 60 | adns this will become the default. | |
| 61 | ||
| 62 | adnshost and the other command-line utilities are fully forward- and | |
| 63 | backward-compatible, except that in adns 1.5, adnshost will return | |
| 64 | IPv6 as well as IPv4 information if simply asked for `addresses'. | |
| 65 | Calling programs which did not ask for a specific address type ought | |
| 66 | to cope with this. | |
| adaee51c IJ |
67 | |
| 68 | The API in 1.5.0 also fixes a technical nonconformance to the C | |
| 69 | specification. On platforms where an `enum' type might be an | |
| 70 | integer type whose size is bits is not a power of two, there could | |
| 71 | be an incompatible ABI change between 1.4 and 1.5 - but we don't | |
| 72 | think there are many (if any) such platforms which are sufficiently | |
| 73 | POSIX-like for adns. (Changed since 1.5.0~rc0.) | |
| 74 |