Hi Vincent, On Thu, Dec 20, 2018 at 10:22:25PM +0100, Vincent Bernat wrote: > ❦ 20 décembre 2018 17:14 +01, Willy Tarreau <w...@1wt.eu>: > > >> this is indeed a regression in haproxy. thanks for reporting it. > >> attached patch should fix it. > >> CC'ing Remi as the original author, and Baptiste, as DNS maintainer. > > > > Good catch, the patch looks obviously good, I've just merged it. > > Thanks for fixing this one, Jérôme. > > Is it important enough for an 1.8.16? Is it important enough for > distributors to release a fixed version? Why doesn't it affect most DNS > implementations?
the bug only triggers when the resolver used by haproxy sends back DNS responses with nothing after the Answers section, ie: no additional records. I'm guessing the use of DNSSEC hides the problem :-) I must get better with commit messages. Jérôme
