unbound 1.9 respone wrong answer (from cache?) when dig +tcp used.

[Punk[D.M]]

Let’s run `dig @127.0.0.1 -p 5300 twitter.com *+tcp*` repeat:



The first answer is ok, but left answer all “empty”



dig say “WARNING: recursion requested but not available”,

kdig say “WARNING: response QR bit not set”



Back to 1.8.3, everthing work fine.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/unbound-users/attachments/20190208/447c3f1c/attachment.htm>