From: Diego Fronza Date: Mon, 31 Aug 2020 16:26:56 +0000 (-0300) Subject: Add CHANGES and release note for GL #1847 X-Git-Tag: v9.17.5~17^2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=044a72cca9912f0b0937588b83f2c9d00fe5a355;p=thirdparty%2Fbind9.git Add CHANGES and release note for GL #1847 --- diff --git a/CHANGES b/CHANGES index b8cb5de6077..6de484a2e37 100644 --- a/CHANGES +++ b/CHANGES @@ -1,3 +1,7 @@ +5495. [bug] With query minimization enabled, named failed to + resolve ip6.arpa. names that had more labels after the + IPv6 part. [GL #1847] + 5494. [bug] Silence the EPROTO syslog message on older systems. [GL #1928] diff --git a/doc/notes/notes-current.rst b/doc/notes/notes-current.rst index c374f0f99c7..422a02b3e0b 100644 --- a/doc/notes/notes-current.rst +++ b/doc/notes/notes-current.rst @@ -45,3 +45,13 @@ Bug Fixes seen on older operating systems where unhandled ICMPv6 errors result in a generic protocol error being returned instead of the more specific error code. [GL #1928] + +- With query minimization enabled, named failed to resolve ip6.arpa. names + that had more labels before the IPv6 part. For example, when named + implemented query minimization on a name like + ``A.B.1.2.3.4.(...).ip6.arpa.``, it stopped at the left-most IPv6 label, i.e. + ``1.2.3.4.(...).ip6.arpa.`` without considering the extra labels ``A.B``. + That caused a query loop when resolving the name: if named received + NXDOMAIN answers, then the same query was repeatedly sent until the number + of queries sent reached the value in the ``max-recursion-queries`` + configuration option. [GL #1847]