Ack. And the development team currently doesn’t have resources to tackle the underlying issue that was causing the assertion failure, so this will only get fixed if we can get a reliable reproducer to the issue (or a patch :)).
Ondrej (with his ISC hat, not Debian Developer hat) -- Ondřej Surý (He/Him) ond...@sury.org > On 21. 1. 2021, at 14:46, Bernhard Schmidt <be...@debian.org> wrote: > > Control: forwarded -1 https://gitlab.isc.org/isc-projects/bind9/-/issues/2091 > > On 30/11/20 11:07 AM, Francesco Potortì wrote: > > Hi, > >> From time to time I get these in the logs: >> >> Nov 29 13:56:15 tucano named[3629893]: resolver.c:5137: unexpected error: >> Nov 29 13:56:15 tucano named[3629893]: '_.edu.cn/A' is not subdomain of >> 'whu.edu.cn' > > As far as I understand > https://gitlab.isc.org/isc-projects/bind9/-/issues/2091 this is part of > the debugging code for an assertion error with earlier 9.16.x versions. > According to upstream this is harmless and it has been mentioned as such > in the release notes of 9.16.11 > > --- > The report of intermittent BIND assertion failures triggered in > lib/dns/resolver.c:dns_name_issubdomain() has now been closed without > further action. Our initial response to this was to add diagnostic > logging instead of terminating named, anticipating that we would receive > further useful troubleshooting input. This workaround first appeared in > BIND releases 9.17.5 and 9.16.7. However, since those releases were > published, there have been no new reports of assertion failures matching > this issue, but also no further diagnostic input, so we have closed the > issue. [GL #2091] > --- > > Please check whether you still see this in 9.16.11 (just uploaded). > > Bernhard >
signature.asc
Description: Message signed with OpenPGP