Hey Nenad,
Actually a local resolver can take care of that for you as well since
every resolver I know allows configuring a different destination on
domain basis. Also as described in the first email, the server has to be
resolvable via the OS resolving stack as well otherwise haproxy won't
start. This means you cannot use custom domains without configuring some
sort of custom resolver anyway.
-Robin-
Nenad Merdanovic wrote on 7/15/2015 08:56:
Hello Robin,
On 07/15/2015 08:49 AM, Robin Geuze wrote:
Tbh I don't really see the point of configuring the resolvers in haproxy
when the OS has perfectly fine working facilities for this? What is the
benefit besides possibly causing lookups to happen twice, once from the
OS resolving stack and once from haproxies? If you really want exactly
the same behavior as described you could always configure a local
resolver that queries multiple other resolvers instead of recursing itself.
Because this would perfectly integrate with things like Consul
(https://www.consul.io/docs/agent/dns.html), which are currently very
widely used to provide service discovery.
-Robin-
Regards,
