mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2025-11-26 21:31:01 +01:00
68a61b6321
DNS resoltions may be triggered via a "do-resolve" action or when a connection failure is experienced during a healthcheck. Cached valid responses are used, if possible. But if the entry is expired or if there is no valid response, a new reolution should be performed. However, an resolution is only performed if the "resolve" timeout is expired. Thus, when this comes from a healthcheck, it means no extra resolution is performed at all. Now, when the resolution is performed for a server (SRV or SRVEQ) and no valid response is found, the resolution timer is reset (last_resolution is set to TICK_ETERNITY). Of course, it is only performed if no resolution is already running. Note that this feature was broken 5 years ago when the resolvers code was refactored (67957bd59e). This patch should fix the issue #1906. It affects all stable versions. However, it is probably a good idea to not backport it too far (2.6, maybe 2.4) and with some delay.
The HAProxy documentation has been split into a number of different files for ease of use. Please refer to the following files depending on what you're looking for : - INSTALL for instructions on how to build and install HAProxy - BRANCHES to understand the project's life cycle and what version to use - LICENSE for the project's license - CONTRIBUTING for the process to follow to submit contributions The more detailed documentation is located into the doc/ directory : - doc/intro.txt for a quick introduction on HAProxy - doc/configuration.txt for the configuration's reference manual - doc/lua.txt for the Lua's reference manual - doc/SPOE.txt for how to use the SPOE engine - doc/network-namespaces.txt for how to use network namespaces under Linux - doc/management.txt for the management guide - doc/regression-testing.txt for how to use the regression testing suite - doc/peers.txt for the peers protocol reference - doc/coding-style.txt for how to adopt HAProxy's coding style - doc/internals for developer-specific documentation (not all up to date)