From: Evan Hunt Date: Wed, 1 Jul 2020 17:59:33 +0000 (-0700) Subject: CHANGES, release note X-Git-Tag: v9.17.4~52^2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=7c703c851f3efc16827a0f96a71766bc46118b8d;p=thirdparty%2Fbind9.git CHANGES, release note --- diff --git a/CHANGES b/CHANGES index f8df942d7dd..4ba2e318644 100644 --- a/CHANGES +++ b/CHANGES @@ -1,3 +1,15 @@ +5467. [func] The control channel and the rndc utility have been + updated to use the new network manager. To support + this, the network manager was updated to enable + wthe initiation of client TCP connections. Its + internal reference counting has been refactored. + + Note: As side effects of this change, rndc cannot + currently be used with UNIX-domain sockets, and its + default timeout has changed from 60 seconds to 30. + These will be addressed in a future release. + [GL #1759] + 5466. [bug] Addressed an error in recursive clients stats reporting. [GL #1719] diff --git a/doc/notes/notes-current.rst b/doc/notes/notes-current.rst index 8aab4540398..1ce674d1e58 100644 --- a/doc/notes/notes-current.rst +++ b/doc/notes/notes-current.rst @@ -24,7 +24,14 @@ Known Issues New Features ~~~~~~~~~~~~ -- None. +- ``rndc`` has been updated to use the new BIND network manager API. + This change had the side effect of altering the TCP timeout for RNDC + connections from 60 seconds to the ``tcp-idle-timeout`` value, which + defaults to 30 seconds. Also, because the network manager currently + has no support for UNIX-domain sockets, those cannot now be used + with ``rndc``. This will be addressed in a future release, either by + restoring UNIX-domain socket support or by formally declaring them + to be obsolete in the control channel. [GL #1759] Feature Changes ~~~~~~~~~~~~~~~