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

[A. Schulze]

Am 08.02.19 um 04:36 schrieb Punk[D.M] via Unbound-users:
> Let’s run `dig @127.0.0.1 <http://127.0.0.1> -p 5300 twitter.com <http://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.

can't reproduce:

$ dig @::1 version.bind. txt ch +short
"unbound 1.9.0"

$ for i in 1 2 3 ; do dig @::1 twitter.com +tcp +short; done
104.244.42.193
104.244.42.65
104.244.42.193
104.244.42.65
104.244.42.65
104.244.42.193

any special configuration / compile options?

Andreas