Re: haproxy doesn't bring failed server up

BTW, all these resolver hold settings are a bit confusing, is there a way to tell haproxy to rely on the TTL it gets from DNS servers/resolvers? It seems to be relying on some hard-coded default values instead. *hold *

Re: haproxy doesn't bring failed server up

On 10/07/2019 11:02 AM, Lukas Tribus wrote: Hello, On Mon, Oct 7, 2019 at 6:30 AM rihad wrote: Thanks! But according to the manual, shouldn't haproxy re-resolve AWS server name regardless of its resolver settings? A few other events can trigger a name resolution at run time: - when a

Re: haproxy doesn't bring failed server up

Hello, On Mon, Oct 7, 2019 at 6:30 AM rihad wrote: > Thanks! But according to the manual, shouldn't haproxy re-resolve AWS server > name regardless of its resolver settings? > > > A few other events can trigger a name resolution at run time: > - when a server's health check ends up in a

Re: haproxy doesn't bring failed server up

Hello, On Mon, Oct 7, 2019 at 10:00 AM rihad wrote: > > BTW, all these resolver hold settings are a bit confusing, is there a way to > tell > haproxy to rely on the TTL it gets from DNS servers/resolvers? It seems to be > relying on some hard-coded default values instead. I don't think TTL is