Date: Wed, 17 Jun 2020 10:36:39 -0700 (PDT) From: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net> To: Barney Wolff <barney@databus.com> Cc: "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net>, Guido Falsi <mad@madpilot.net>, Andriy Gapon <avg@freebsd.org>, Eugene Grosbein <eugen@grosbein.net>, net@freebsd.org Subject: Re: unbound and (isc) dhcpd startup order Message-ID: <202006171736.05HHad0M086370@gndrsh.dnsmgr.net> In-Reply-To: <20200616180435.GA77624@pit.databus.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Tue, Jun 16, 2020 at 08:18:59AM -0700, Rodney W. Grimes wrote: > > ... Sometimes > > that leads to duplicate IP information stored in various config files. > > > > When possible managing those configuraitons via ansible or other CM > > system that can pull the data from dns and build the config files > > minimizes the work to keep it all up to date. > > Would defining a variable in /etc/rc.conf help? Don't most/all rc.d scripts end up sourcing it? Works for me in my local startups. No as it is usually .conf files that need this info, and those do not source rc.conf. Almost any routing protocol configuration needs access to this data, dhcpd.conf is another one. This particular one, wanting to use names in a name service itself is particularly hard to deal with. -- Rod Grimes rgrimes@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202006171736.05HHad0M086370>