Humm, feeling ashamed I did not quite realized what was going on here. Since my system has changed behaviour since upgrade I (wrongly) concluded the issue was dig. The issue is due the upgrade that replaced my cache dns with dnsmasq ... and now it seems this one is the culprit.
I'll investigate further and post another report if needed, 'till then feel free to close the report. Sorry for the inconvenience -- 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/1277467 Title: dig 9.9.3 behave differently than previous version on SOA record To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1277467/+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
