I second this opinion. Removing ANY altogether would be the best case. In reality, I think it should use the OS's resolver libraries which in turn will honor whatever the admin has configured for preference order at the base OS level.
As a sysadmin, one should reasonably expect that tweaking the preference knob at the OS level should affect most (and ideally, all) applications they are running rather than having to manually fiddle knobs at the OS and various application levels. If there is some discussion and *good* reasons to ignore the OS defaults, I feel this should likely be an *optional* config option in haproxy.cfg ie "use OS resolver, unless specifically told not to for $reason) On Thu, Oct 15, 2015 at 11:32 AM, Lukas Tribus <[email protected]> wrote: >> Jan, a fellow HAProxy user, already reported me that ANY query types >> are less and less fashion (for many reasons I'm not going to develop >> here). >> >> Amongs the many way to fix this issue, the one below has my preference: >> A new resolvers section directive (flag in that case) which prevent >> HAProxy from sending a ANY query type for the nameservers in this >> section ie "option dont-send-any-qtype". > > Actually, I would remove ANY altogether: > > ANY will provide wrong results on RFC-compliant recursive resolvers, > more often than not. > > For example, if an A record is in the cache, but an AAAA is > not cached, ANY will only return A, even if we "resolve-prefer" > ipv6. > > It makes no sense to keep it, especially if it remains default. > > > > Regards, > > Lukas > > > > > -- Jeff Palmer https://PalmerIT.net
