[question] 9.18.4 fails processing certain query reply with: 'end of file'
Summary
Working for an ISP which recently updated it's caching and recursive NS to bind 9.18.4 we got a report from a customer which could not resolve a specific resource: fd19g0409.drive.pro.io
BIND version used
9.18.4
Steps to reproduce
$ dig +noedns +nocookie +nodnssec +noednsnegotiation A fd19g0409.drive.pro.io @{BIND-9.18.4-NS}
Setting various options likely to pin down causes of similar issues. No success.
Consult Syslog on Bind DNS and find error:
named[3156696]: end of file resolving '_.drive.pro.io/A/IN': 80.74.143.169#53
Analyzing traffic with Wireshark shows the authoritative server in question is answering the query and the reply IMHO is correct.
What is the current bug behavior?
Bind 9.18.4 most probably fails parsing the reply with 'End of File' Error thus ignoring the reply. They query is repeated a couple of times, then a timeout 'SERVERFAIL' is returned to the client.
What is the expected correct behavior?
Using Bind 9.11.36 with the same query works flawlessly. Using other DNS resolves works flawlessly.
=> A record of: fd19g0409.drive.pro.io is returned.
Relevant configuration files
I don't think this is relevant. It could be reproduced by others.
Relevant logs and/or screenshots
named[3156696]: end of file resolving '_.drive.pro.io/A/IN': 80.74.143.169#53
Asked on SWINOG Mailinglist if colleagues at other ISP could reproduce the issue or could spot the cause.
Result: Got report from a colleague: Bind 9.18.7 fails the same way. Got several reports that nobody can spot an issue with the reply in question which would cause bind to fail to parse this reply. Got a hint, that it might be related to issue: #3474 (closed) Others suspect this looks like a Bug in Bind 9.18.X