That's totally understandable of course, but maybe this could be enabled via an option ?
It's just a suggestion. After all, if I want no DNS lookup I'd rather put only IPs on my "server" line. On Wed, Jun 9, 2010 at 1:43 PM, David Birdsong <[email protected]>wrote: > On Wed, Jun 9, 2010 at 12:57 PM, Mathieu Oudart <[email protected]> > wrote: > > Hi, > > > > i'm using haproxy to loadbalance web frontends on Amazon EC2. I use a > server > > line like : > > server app1 frontend1.example.com:80 check inter 5000 > > > > Whenever I restart a frontend, it gets another IP so I update the > > frontend1.example.com DNS record accordingly. > > > > The issue is that haproxy never detect the change. It keeps polling the > old > > IP and marks the server "down" until I manually reload the HAproxy > service. > > > > Is there an option to handle that and detect the dynDNS change > automatically > > ? > > > > AFAIK, haproxy does any dns resolution once at start and never again > -which is desirable, adding a dns lookup to each request would be very > costly. > > > Thanks. > > -- > > Mathieu OUDART > > > -- -- Mathieu OUDART
