named and ntpd start order in rc.d

[RW]

On Sun, 26 Aug 2018 18:34:43 +0200
Andrea Venturoli wrote:

> Hello.
> 
> I'm in the same situation described in this bug:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=129146
> 
> ntpd starts when named is not yet running, fails to resolve its peers 
> and never works again until I restart it manually.
> 
> That bug (of the 7.0 era) was closed as fixed, since /etc/rc.d/ntpd 
> requires ntpdate, which in turn required named.
> However, the latest statement is not true anymore, today (probably
> due to the fact that named is no longer in base).

What's in base looks OK

rcorder /etc/rc.d/* |egrep  'ntp|unbou|NET'
/etc/rc.d/local_unbound
/etc/rc.d/NETWORKING
/etc/rc.d/ntpdate
/etc/rc.d/ntpd


local_unbound starts before NETWORKING and ntpdate requires NETWORKING

check where bind fits in when you run 

 rcorder /etc/rc.d/*  /usr/local/etc/rc.d/*

If it's out of correct order I'd suggest opening a new bug report
against the bind port.

If it's already correct try enabling netwait in rc.conf.