Fwd: unresolvable host names as error

2012-05-12 Thread Andres Thomas Stivalet
On Fri, May 11, 2012 at 3:32 PM, Baptiste bed...@gmail.com wrote: On Fri, May 11, 2012 at 6:09 PM, Andres Thomas Stivalet atstiva...@gmail.com wrote: Currently, if haproxy tries to start up and a webserver is down (and it's defined as a hostname in the config file) haproxy refuses to start

Re: unresolvable host names as error

2012-05-12 Thread Andres Thomas Stivalet
Hi Willy, I believe in previous versions of haproxy having an unresolvable host name at start up did not cause haproxy to error out. Bellow is the change log I found: 2010/03/30 : 1.3.24 - [BUG] config: report unresolvable host names as errors I wrongly assumed that haproxy performed DNS

Re: Fwd: unresolvable host names as error

2012-05-12 Thread Andres Thomas Stivalet
PM, Willy Tarreau w...@1wt.eu wrote: On Sat, May 12, 2012 at 02:53:45PM -0500, Andres Thomas Stivalet wrote: That's why I've added this to the TODO list :-) Thanks Willy! For the same reason, you cannot safely install firewalls nor VPNs in such environments. I'd just like

unresolvable host names as errors

2012-04-27 Thread Andres Thomas Stivalet
Currently, if haproxy tries to start up and a webserver is down (and it's defined as a hostname in the config file) haproxy refuses to start. Looking at the previous change logs and announcements it seems this is by design. Why is this done and is there a way to circumvent this? Cheers