unbound and (isc) dhcpd startup order

[Rodney W. Grimes]

> On 15/06/20 14:47, Andriy Gapon wrote:
> > On 15/06/2020 14:48, Eugene Grosbein wrote:
> >> 15.06.2020 13:10, Andriy Gapon wrote:
> >>
> >>> I am configuring a small LAN -- mostly a gateway / router for it -- and I am
> >>> using unbound for a local DNS and isc-dhcp44-server for DHCP.
> >>> I have a few hosts with static IP addresses (for various reasons).
> >>> So, in unbound.conf I have an entry like
> >>>   local-data: "hipster.home.arpa. IN A 192.168.0.222"
> >>
> >> Consider using /etc/hosts in addition to DNS to solve chicken/egg problem.
> >>
> >>
> > 
> > Having the same IP in more than one place (on the router) is the thing that I'd
> > like to avoid in the first place.  Otherwise, there is no problem putting it in
> > hdcpd.conf.
> > 
> 
> A secondary DNS server could also help, unless both are rebooted at the
> same time.

Defanitly, that is one solution, but it also has issues like now I need
NETWORKING and ROUTING and FIREWALL code all working before I might be
able to access that "remote" DNS server.

This is one of the things that has lead me to manage systems in a way
that I can almost  always boot anything with the network disconected
and it still comes up with a valid and operation state.  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.

> -- 
> Guido Falsi <mad at madpilot.net>
-- 
Rod Grimes                                                 rgrimes at freebsd.org