Hello Jim. I've seen the thread and that you're "befuddled" a little about the use of DNS.,
Think of it this way, with the resolvers in HAProxy you can resolve the real server names of real server pool, this may be very dynamic in nature and separate to /etc/resolve.conf Now imagine a farm of Haproxy servers with different resolves configured internally, but you want the Haproxy instance to have public DNS resolved while there may be many split horizon dns available and maybe not public. Haproxy then ensures it uses the DNS servers you want it to and not the system resolver Personally and this is just an opinion I think the Haproxy resolver is and should be separate to /etc/resolv.conf Andruw Smalley Loadbalancer.org Ltd. www.loadbalancer.org +1 888 867 9504 / +44 (0)330 380 1064 [email protected] Leave a Review | Deployment Guides | Blog On 29 December 2017 at 21:26, Lukas Tribus <[email protected]> wrote: > Hi Jim, > > > On Fri, Dec 29, 2017 at 10:14 PM, Jim Freeman <[email protected]> wrote: >> Looks like libresolv 's res_ninit() parses out /etc/resolv.conf 's >> nameservers [resolv.h], so haproxy won't have to parse it either ... >> >> Will keep poking. > > Do give it some time to discuss the implementation here first though, > before you invest a lot of time in a specific direction (especially if > you link to new libraries). > > CC'ing Baptise and Willy. > > > > cheers, > lukas >
