Re: Fwd: unresolvable host names as error

2012-05-13 Thread Willy Tarreau
Hi Aleks, On Sun, May 13, 2012 at 09:43:40AM +0200, Aleksandar Lazic wrote: Be careful, if you want to implement a resolver, you can't use the libc's since the process is supposed to be chrooted, so you'll need to implement an autonomous resolver with an IP address to be used as the DNS

Re: Fwd: unresolvable host names as error

2012-05-13 Thread Aleksandar Lazic
Hi Willy, On 13-05-2012 11:00, Willy Tarreau wrote: Hi Aleks, On Sun, May 13, 2012 at 09:43:40AM +0200, Aleksandar Lazic wrote: Be careful, if you want to implement a resolver, you can't use the libc's since the process is supposed to be chrooted, so you'll need to implement an autonomous

Fwd: unresolvable host names as error

2012-05-12 Thread Andres Thomas Stivalet
Sometimes it would be resolvable and other times not, it depends if the host has reported itself to the DNS server previously and it's still in the bind cache after going down. I suspect that this is happening if the host is down and there is no IP for it in the DNS tables, but that's just guess

Re: Fwd: unresolvable host names as error

2012-05-12 Thread Willy Tarreau
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 to mention that it's certainly possible to

Re: Fwd: unresolvable host names as error

2012-05-12 Thread Andres Thomas Stivalet
Given how the current farm toolset operates under the hostname assumption we're still going to have change hostnames etc. We're currently evaluating if we want to patch haproxy for our needs or track our machines some other way. Patching haproxy seems like the sane route. :) On May 12, 2012 3:17