Hello,
On Fri, Dec 29, 2017 at 7:00 PM, Jim Freeman <[email protected]> wrote: > I'm a bit befuddled by the different nameserver config 'twixt these 2 modes? > [ Methinks I grok the need for an internal non-libc/libresolv resolver ] > > Why isn't the the /etc/resolv.conf start-time config used (or at least > available) as a default run-time config (chroot notwithstanding)? > Under what circumstances do nameservers/settings need to be different in > start vs. run modes? Haproxy never reads in /etc/resolv.conf; libc does it for us (for libc based resolution). > I'd expect that for most installations, the run-time config could/should be > the same as the start-time config ? Having to create a run-time config that > will just be the same as the start-time gets in the way of automating of > config across different environments ... I can see it wouldn't scale if you have a large number of different nameserver sets. I guess that is not usually a problem and people have the same name servers sets or at least provisioning groups using the same nameserver sets, so automation can handle it in a scalable way. Or they automate it away in other ways, like with placeholders in haproxy.cfg and scripts that replace the placeholders locally. I can certainly see how this would simplify things, but writing a /etc/resolv.conf parser in userspace is something that I would consider a specific feature for which someone has to write actual code for it. nginx does not parse resolv.conf either, btw: http://nginx.org/en/docs/http/ngx_http_core_module.html#resolver Lukas
