- 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

- Remove virtual interfaces after testsuite

• Files Changed
• Browse Source

- Update to release 9.19.12
  Security Fixes:
  * An error in DNS message processing introduced in development
    version 9.19.11 could cause BIND and its utilities to crash if
    the maximum permissible number of DNS labels were present. This
    has been fixed.
  Known Issues:
  * Loading a large number of zones is significantly slower in BIND
    9.19.12 than in the previous development releases due to a new
    data structure being used for storing information about the
    zones to serve. This slowdown is considered to be a bug and
    will be addressed in a future BIND 9.19.x development release.
  * A flaw in reworked code responsible for accepting TCP
    connections may cause a visible performance drop for TCP
    queries on some platforms, notably FreeBSD. This issue will be
    fixed in a future BIND 9.19.x development release.
  New Features:
  * BIND now depends on liburcu, Userspace RCU, for lock-free data
    structures.
  * The new command-line delv +ns option activates name server
    mode, to more accurately reproduce the behavior of named when
    resolving a query. In this mode, delv uses an internal
    recursive resolver rather than an external server. All messages
    sent and received during the resolution and validation process
    are logged. This can be used in place of dig +trace.
  * A new configuration option, checkds, has been introduced. When
    set to yes, it detects parental-agents automatically by
    resolving the parent NS records. These name servers are queried
    to check the DS RRset during a KSK rollover initiated by
    dnssec-policy.

• Files Changed
• Browse Source

- Update to release 9.19.11
- Update bind.keyring
- Remove libbind9*.so and libirs*.so from bind-utils files
  * The functions of libbind9 have been moved to libisc and
    libisccfg
  * The functions of libirs have been moved to libdns
- Remove bind.keys
  * This is now precompiled into bind and thus not shipped anymore.

• Files Changed
• Browse Source

- Update to release 9.19.7

• Files Changed
• Browse Source

• Browse Source