It's interesting that the default behavior of HAProxy resolvers can
conflict with the default behavior of bind. (If you're unlucky with
whatever bind has cached)

By default, bind uses case-insensitive compression, which can cause it to
use a different case in the ANSWER than in the QUESTION. (See
'no-case-compress': We were
impacted by this recently.

Also interesting:

On Mon, Apr 9, 2018 at 2:12 AM, Baptiste <> wrote:

> So, it seems that responses that does not match the case should be dropped:
> Baptiste

Reply via email to