tree e9f199ca4a6aebb76d9eda8077bac83213228e03
parent e3ec217d457e8ec987467a550bb139ee9924b1a4
author William Lallemand <wlallemand@haproxy.com> 1702899335 +0100
committer Christopher Faulet <cfaulet@haproxy.com> 1705071183 +0100

BUG/MINOR: resolvers: default resolvers fails when network not configured

Bug #1740 was opened again, this time a user is complaining about the
"can't create socket for nameserver". This can happen if the resolv.conf
file contains a class of address which was not configured on the
machine, for example IPv6.

The fix does the same as b10b1196b ("MINOR: resolvers: shut the warning
when "default" resolvers is implicit"), and uses the
"resolvers->conf.implicit" variable to emit the error.

Though it is not needed to convert the explicit behavior with a
ERR_WARN, because this is supposed to be an unrecoverable error, unlike
the connect().

Should fix issue #1740.

Must be backported were b10b1196b was backported. (as far as 2.6)

(cherry picked from commit 0d2ebb53f752502137479c9e753a96046d3254ab)
Signed-off-by: Willy Tarreau <w@1wt.eu>
(cherry picked from commit 49242213556fa35f690698cd8aac6324370c4652)
Signed-off-by: Christopher Faulet <cfaulet@haproxy.com>