I also confirm this bug. More over I would suggest to raise this bug to an important.
Whenever user tries to use bind9 as recursive dns (i think it is about a half of use cases) and when that user have only IPv4 connection (i think it is 90% of use cases now) user will get a lot of network error messages in a log as it will not be able to connect to IPv6 NS hosts: фев 26 15:25:41 bind named[72]: error (network unreachable) resolving 'www.debian.org/A/IN': 2001:41b8:202:deb:1a1a:0:52c3:4b69#53 фев 26 15:25:41 bind named[72]: error (network unreachable) resolving 'org/DNSKEY/IN': 2001:500:40::1#53 The only way to avoid this, is to run bind9 with -4 option. Theoretically it should be done by specifying it in /etc/default/bind9 file in OPTIONS option. But this does not work. So approximately 45% of users are not able to get rid of error messages in error log. This is really bad, I think. Please fix it. The solution is known. Just test and apply it!
