Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Aug 2018 02:09:44 +0300
From:      Yuri Pankov <yuripv@yuripv.net>
To:        Andrea Venturoli <ml@netfence.it>, freebsd-questions@freebsd.org
Subject:   Re: named and ntpd start order in rc.d
Message-ID:  <cdabc46e-8a93-06eb-6867-dcc7cf0a44cd@yuripv.net>
In-Reply-To: <e651e86a-76d4-391c-9d38-9be8448bb455@netfence.it>
References:  <e651e86a-76d4-391c-9d38-9be8448bb455@netfence.it>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
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.

This seems to be a real bug here.  Sometimes I'm seeing the ntpd whining 
about resolve failures on start when I'm doing network maintenance, but 
I have never checked if it operates correctly once the nameservers are back.

Did you look into *why* it never works again, and how exactly it doesn't 
work -- it still seems to be running and spamming console while it's 
unable to resolve?

> 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).
> 
> I guess I'm not the only one who has this problem and I wonder how 
> others are solving this issue.
> Also, should I add a comment to that bug or open a new one?



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?cdabc46e-8a93-06eb-6867-dcc7cf0a44cd>