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 <https://cbonte.github.io/haproxy-dconv/2.0/configuration.html#5.3.2-hold>* <status> <period>

Defines <period> during which the last name resolution should be kept based
on last resolution <status>
  <status> : last name resolution status. Acceptable values are "nx",
             "other", "refused", 
"timeout<https://cbonte.github.io/haproxy-dconv/2.0/configuration.html#>", "valid", "obsolete".
  <period> : interval between two successive name resolution when the last
             answer was in <status>. It follows the HAProxy time format.
             <period> is in milliseconds by default.

Default value is 10s for "valid", 0s for "obsolete" and 30s for others.

Reply via email to