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
No problem; thank you for confirming.
** Changed in: bind9 (Ubuntu)
Status: Incomplete = Invalid
--
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
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
In your example, you haven't specified which server dig should query,
and I can see that the responses have come from different servers. I
don't see any documentation that states that server selection should be
