Bind DNS Bugfix Release 9.18.15 und 9.16.41 veröffentlicht

Der Open-Source DNS Server BIND erhielt je Zweig ein Update und liegt nun in der Version 9.16.41 bzw. 9.18.15 vor.

Bind 9.18.15 ESR Release Notes

Bug Fixes

• The max-transfer-time-in and max-transfer-idle-in statements have not had any effect since the BIND 9 networking stack was refactored in version 9.16. The missing functionality has been re-implemented and incoming zone transfers now time out properly when not progressing. [GL #4004]
• The read timeout in rndc is now 60 seconds, matching the behavior in BIND 9.16 and earlier. It had previously been lowered to 30 seconds by mistake. [GL #4046]
• When the ISC_R_INVALIDPROTO (ENOPROTOOPT, EPROTONOSUPPORT) error code is returned by libuv, it is now treated as a network failure: the server for which that error code is returned gets marked as broken and is not contacted again during a given resolution process. [GL #4005]
• When removing delegations from an opt-out range, empty-non-terminal NSEC3 records generated by those delegations were not cleaned up. This has been fixed. [GL #4027]
• Log file rotation code did not clean up older versions of log files when the logging channel had an absolute path configured as a file destination. This has been fixed. [GL #3991]

Known Issues

• Sending NOTIFY messages silently fails when the source port specified in the notify-source statement is already in use. This can happen e.g. when multiple servers are configured as NOTIFY targets for a zone and some of them are unresponsive. This issue can be worked around by not specifying the source port for NOTIFY messages in the notify-source statement; note that source port configuration is already deprecated and will be removed altogether in a future release. [GL #4002]
• See above for a list of all known issues affecting this BIND 9 branch.

Bind 9.16.41 ESR Release Notes

Bug Fixes

• When removing delegations from an opt-out range, empty-non-terminal NSEC3 records generated by those delegations were not cleaned up. This has been fixed. [GL #4027]

Known Issues

• There are no new known issues with this release. See above for a list of all known issues affecting this BIND 9 branch.

Quelle: BIND 9 – ISC