Slawa,
I have a question below :
backend default-pool
balance roundrobin
option httpchk GET /health-check
timeout connect 1000ms
timeout server 5000ms
server elb1 x.eu-west-1.elb.amazonaws.com:80 maxconn 7000 id 1 check
resolvers mydns resolve-prefer ipv4
server elb2 y.eu-west-1.elb.amazonaws.com:80 maxconn 7000 id 2 check
resolvers mydns resolve-prefer ipv4
(...)
resolvers mydns
nameserver dns1 8.8.8.8:53
resolve_retries 3
timeout retry 1s
hold other 30s
hold refused 30s
hold nx 30s
hold timeout 30s
hold valid 10s
Do you think the issue described below could have any effect on your use
case, such as forcing frequent changes, updates or up/down ? Just trying
to narrow down the possible trigger for the problem (I still failed to
see it for now, even after sending lots of HTTP traffic and DNS responses) :
https://www.reddit.com/r/sysadmin/comments/8ejrkk/google_dns_issues/
Thanks,
Willy
