- Update to release 9.18.15
  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.
  * 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.
  * 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.
  * 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.
  * 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.
  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.

• Files Changed
• Browse Source