Version 9.18.1 Receives FORMERR from Windows DNS Server
Summary
On v9.18.1, when BIND issues an ordinary query to an authoritative Windows DNS Server (6.1.7601 and earlier), a FORMERR is returned.
BIND version used
9.18.1
Steps to reproduce
dig @<9.18.1-recursive-server> support.leicams.com
dig @<9.18.1-recursive-server> www.blackhawkengineers.com
What is the current bug behavior?
dig will answer with a SERVFAIL but the log record reports a FORMERR and a WireShark capture shows a FORMERR. (Including +noedns or +nocookie does not make a difference.)
; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.8 <<>> @dns1.fsu.edu support.leicams.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 20375
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;support.leicams.com. IN A
BIND Log Record:
view internal: query failed (FORMERR) for support.leicams.com/IN/A at query.c:7662
WireShark Capture:
Flags:
.... .... .... 0001 = Reply code: Format error (1)
What is the expected correct behavior?
When the same query is issued to a 9.11.37 or 9.16.27 server you get an answer:
; <<>> DiG 9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.8 <<>> @dnsa1.fsu.edu support.leicams.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56585
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;support.leicams.com. IN A
;; ANSWER SECTION:
support.leicams.com. 7200 IN A 195.63.85.52
Relevant configuration files
Relevant logs and/or screenshots
BIND Log Record:
view internal: query failed (FORMERR) for support.leicams.com/IN/A at query.c:7662
WireShark Capture:
Flags:
.... .... .... 0001 = Reply code: Format error (1)