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

Unbound
1

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.

2

My size 1.9.0 is ok with your query:

dig twitter.com +tcp

; <<>> DiG 9.6-ESV-R11-S10 <<>> twitter.com +tcp
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63383
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;twitter.com. IN A

;; ANSWER SECTION:
twitter.com. 2936 IN A 104.244.42.193
twitter.com. 2936 IN A 104.244.42.65

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Fri Feb 08 21:32:07 +06 2019
;; MSG SIZE rcvd: 61

3

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

4

Hi,

5

This seems to be bug#4225, for which there is a fix in the code
repository. It was just fixed an hour ago. The patch for it is this, I
think:

Hello Wouter,

https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=4225
also mention an other fix in qname minimisation.

do you suggest to apply both or will there a next version soon?

Andreas

6

Hi Andreas,

This seems to be bug#4225, for which there is a fix in the code
repository. It was just fixed an hour ago. The patch for it is this, I
think:

Hello Wouter,

https://www.nlnetlabs.nl/bugs-script/show_bug.cgi?id=4225
also mention an other fix in qname minimisation.

do you suggest to apply both or will there a next version soon?

Of course, I want both in a release. But the patch I show I think
solves the issue that that user has. (The user reported privately that
the latest code repo version indeed solves his problems).

Apply both is certainly fine, the qname minimisation fix is good to
have. I do not have a specific release timeline in mind.

Best regards, Wouter