Hi Lukas,
Thanks for your help!
> On Mar 10, 2025, at 21:49, Lukas Tribus <lu...@ltri.eu> wrote:
>
> It's a blocking syscall, I don't think there is anything that can be
> done about it.
>
> Your use case matches "init-addr none" (or last,none): only the
> haproxy resolver will be used, haproxy will not refuse to start and
> will not depend on libc name resolution.
That makes sense. We'll make that change.
>
> Mixing libc and resolver resolution is imo always dangerous. libc
> resolution can hide resolver issues, which than become harder to
> diagnose and vice versa.
I think the docs could be updated to reflect this. The current docs are quite
unclear in the pitfalls of mixing the two, especially since the example has the
following and the docs for init-add don't mention resolvers at all:
defaults
# never fail on address resolution
default-server init-addr last,libc,none
>
> But libc based name resolution behavior itself is never up to haproxy,
> but OS/libc configuration.
Fair enough. :) There a timeout option for resolv.conf which we found, but I
think moving to entirely depending on HAProxy resolvers is the best option
anyways.
> Lukas
—
Luke Seelenbinder
Stadia Maps | Founder & CEO
stadiamaps.com
