- Update to release 9.19.13
  New Features:
  * dnstap-read can now print long timestamps with millisecond
    precision.
  Bug Fixes:
  * When the same notify-source address and port number was
    configured for multiple destinations and zones, an unresponsive
    server could tie up the relevant network socket until it timed
    out; in the meantime, NOTIFY messages for other servers
    silently failed. named will now retry sending such NOTIFY
    messages over TCP. Furthermore, NOTIFY failures are now logged
    at the INFO level.
  * The max-transfer-time-in and max-transfer-idle-in 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.
  * A flaw in reworked code responsible for accepting TCP
    connections has been addressed. This issue could cause a

• Files Changed
• Browse Source