bind 9.11.0-2.P3 announcement

[M2]

I have a strange situation here: DiG 9.11.0-P3 does not work, but 
nslookup does.
Target server XXX.220.6.135 is a Windows domain controller with the 
following versions:

$ dig @160.220.6.135 version.bind txt chaos
 > ;; Warning: query response not set
 > ;; Warning: Message parser reports malformed message packet.
 >
 > ; <<>> DiG 9.11.0-P3 <<>> @160.220.6.135 version.bind txt chaos
 > ; (1 server found)
 > ;; global options: +cmd
 > ;; Got answer:
 > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45408
 > ;; flags: aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
 > ;; WARNING: recursion requested but not available
 >
 > ;; QUESTION SECTION:
 > ;version.bind.                  CH      TXT
 >
 > ;; ANSWER SECTION:
 > version.bind.           1476526080 IN   TXT     "Microsoft DNS 
6.1.7601 (1DB14556)"
 >
 > ;; Query time: 15 msec
 > ;; SERVER: 160.220.6.135#53(160.220.6.135)
 > ;; WHEN: Wed Mar 01 15:27:38 WEST 2017
 > ;; MSG SIZE  rcvd: 76

Same, using nslookup

$ nslookup -type=txt -class=chaos version.bind XXX.220.6.135
 > ;; Warning: query response not set
 > ;; Warning: Message parser reports malformed message packet.
 > Server:         160.220.6.135
 > Address:        160.220.6.135#53
 >
 > version.bind    text = "Microsoft DNS 6.1.7601 (1DB14556)"


Now, the unexplained behaviour:

$ dig @XXX.220.6.135 smtprelay.ZZZZZZ.it
 >
 > ; <<>> DiG 9.11.0-P3 <<>> @XXX.220.6.135 smtprelay.ZZZZZZ.it
 > ; (1 server found)
 > ;; global options: +cmd
 > ;; Got answer:
 > ;; ->>HEADER<<- opcode: QUERY, status: FORMERR, id: 62354
 > ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
 > ;; WARNING: recursion requested but not available
 >
 > ;; OPT PSEUDOSECTION:
 > ; EDNS: version: 0, flags:; udp: 4096
 > ; COOKIE: 4ed26dfbce8644f9 (echoed)
 > ;; QUESTION SECTION:
 > ;smtprelay.ZZZZZZ.it.           IN      A
 >
 > ;; Query time: 31 msec
 > ;; SERVER: XXX.220.6.135#53(XXX.220.6.135)
 > ;; WHEN: Wed Mar 01 15:16:58 WEST 2017
 > ;; MSG SIZE  rcvd: 60

However, nslookup can resolve the same name against the same server:

 > $ nslookup smtprelay.ZZZZZZ.it XXX.220.6.135
 > Server:         XXX.220.6.135
 > Address:        XXX.220.6.135#53
 >
 > Non-authoritative answer:
 > Name:   smtprelay.ZZZZZZ.it
 > Address: XXX.88.79.139

and cacheing is not the issue:

$ dig @XXX.220.6.135 smtprelay.ZZZZZZ.it
 > ; <<>> DiG 9.11.0-P3 <<>> @XXX.220.6.135 smtprelay.ZZZZZZ.it
 > ; (1 server found)
 > ;; global options: +cmd
 > ;; Got answer:
 > ;; ->>HEADER<<- opcode: QUERY, status: FORMERR, id: 45458
 > ;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
 > ;; WARNING: recursion requested but not available
 >
 > ;; OPT PSEUDOSECTION:
 > ; EDNS: version: 0, flags:; udp: 4096
 > ; COOKIE: 3fe950fb090b3c46 (echoed)
 > ;; QUESTION SECTION:
 > ;smtprelay.ZZZZZZ.it.           IN      A
 >
 > ;; Query time: 93 msec
 > ;; SERVER: XXX.220.6.135#53(XXX.220.6.135)
 > ;; WHEN: Wed Mar 01 15:17:11 WEST 2017
 > ;; MSG SIZE  rcvd: 60
 >

DIG version 9.10 worked.
Regards, Mauro




--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple