information about each release, source code, and pre-compiled versions
for Microsoft Windows operating systems.
-.. include:: ../notes/notes-current.rst
+.. include:: ../notes/notes-9.17.9.rst
.. include:: ../notes/notes-9.17.8.rst
.. include:: ../notes/notes-9.17.7.rst
.. include:: ../notes/notes-9.17.6.rst
Notes for BIND 9.17.9
---------------------
-Security Fixes
-~~~~~~~~~~~~~~
-
-- None.
-
-Known Issues
-~~~~~~~~~~~~
-
-- None.
-
New Features
~~~~~~~~~~~~
- ``ipv4only.arpa`` is now served when DNS64 is configured. [GL #385]
-Removed Features
-~~~~~~~~~~~~~~~~
-
-- A number of non-working configuration options that had been marked
- as obsolete in previous releases have now been removed completely.
- Using any of the following options is now considered a configuration
- failure:
- ``acache-cleaning-interval``, ``acache-enable``, ``additional-from-auth``,
- ``additional-from-cache``, ``allow-v6-synthesis``, ``cleaning-interval``,
- ``dnssec-enable``, ``dnssec-lookaside``, ``filter-aaaa``,
- ``filter-aaaa-on-v4``, ``filter-aaaa-on-v6``, ``geoip-use-ecs``, ``lwres``,
- ``max-acache-size``, ``nosit-udp-size``, ``queryport-pool-ports``,
- ``queryport-pool-updateinterval``, ``request-sit``, ``sit-secret``,
- ``support-ixfr``, ``use-queryport-pool``, ``use-ixfr``. [GL #1086]
-
Feature Changes
~~~~~~~~~~~~~~~
signal that the entire DS RRset at the parent must be removed, as
described in RFC 8078. [GL #1750]
-- The default value of ``max-stale-ttl`` has been changed from 12 hours to 1
- day and the default value of ``stale-answer-ttl`` has been changed from 1
- second to 30 seconds, following RFC 8767 recommendations. [GL #2248]
-
- When using the ``unixtime`` or ``date`` method to update the SOA
serial number, ``named`` and ``dnssec-signzone`` silently fell back to
the ``increment`` method to prevent the new serial number from being
those releases were published, there have been no new reports of
assertion failures matching this issue, but also no further diagnostic
input, so we have closed the issue. [GL #2091]
-
-- KASP incorrectly set signature validity to the value of the DNSKEY signature
- validity. This is now fixed. [GL #2383]