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

Punk[D.M] punkdm at gmail.com
Fri Feb 8 03:36:15 UTC 2019

Let’s run `dig @ -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>

More information about the Unbound-users mailing list