It means that a small number of domains that used to resolve perfectly fine prior to Lucid, no longer work (due to the stricter handling of the 'aa' flag). I run caching resolvers for an ISP; all the time we're on an affected version of BIND, our customers can't access specific domains. Very few specific examples have been raised through support thus far, but we've only been on Lucid for a couple of weeks.
If the fix can't be reasonably backported, we'll likely move to non-LTS releases and retarget 12.04LTS when it's available. Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/807324 Title: BIND 9.7.0 (ie., lucid) is overly strict on authoritative responses missing the "aa" flag To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/807324/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
