Error in Bind 9.16.17, leading to incorrect processing W symbol in DNS queries

published Corrective updates of the stable DNS server branch Bind 9.16.18 And in the development of an experimental branch 9.17.15, in which Eliminated Serious Error , which appeared in Bind issues 9.16.17 and 9.17.14, published last week (the next day after these releases, the developers warned about the presence of a problem and recommended not to install versions 9.16.17 and 9.17.14).

in versions 9.16.17 and 9.17.14 in the tables of symbols in the lower and top register (MAPToupper and Maptolower) It was Missed The character “w”, which led to the replacement of “W” and “W” characters in the domain names to the ” ” sequence and returning an incorrect result when processing the mask requests. For example, if a record “* .sub.test.local” was present in the DNS zone. 1 A 127.0.0.1 “Quick name” UVW.Sub.Test.local “led to the conclusion of an answer in which the name” UV / 000.Sub was returned. test.local “Instead of” uvw.sub.test.local “.

In addition,

Update Publication 9.16.18 was detained due to the identification of still two Errors , which remained not eliminated in versions 9.16.18 and 9.17.15. Errors lead in the occurrence of mutual blocking during initialization and manifest themselves in configurations in which the same zones are used in DNSEC-Policy (View). Users with similar settings are recommended to roll back to the Bind 9.16.16 version.

/Media reports.