@rmohr wrote:
Hi,
We are using the haproxy resolvers feature. It works awesome, but I would be grateful to get some clarifications on what haproxy does if it can't reache the DNS server(s) or DNS servers don't provide the requested dns entry.
The main issue we seem to have is that haproxy stops to ask the DNS server if it can resolve a hostname forever in some scenarios.
Our setup looks like this:
resolvers kubernetes
nameserver skydns ${DNS}:53
resolve_retries 10
timeout retry 2s
hold valid 30sbackend servers
mode http
timeout connect 10s
timeout server 1m
balance roundrobin
server host1 virt-api-service:8183 resolvers kubernetes"$DNS" points to the kubernetes dns server, "virt-api-service" is sooner or later resolvable over this $DNS server, but when we start the application we can't guarantee that the DNS server is already reachable and if it is, we can't guarantee that it already knows about "virt-api-server".
How would you configure the resolvers to deal with such situations?
If I understand https://cbonte.github.io/haproxy-dconv/configuration-1.6.html#5.3.2 correct, it might be that it is not possible. Could that be?
Best Regards,
Roman
Posts: 7
Participants: 2