Re: [chrony-users] Chrony forgets servers (specified by FQDN) when no DNS server

[ Thread Index | Date Index | More chrony.tuxfamily.org/chrony-users Archives ]


Stephen Satchell wrote:
On 12/20/2017 11:51 AM, Rob Janssen wrote:
A time server that uses DNS based rules for reference servers should fail gracefully when the DNS does not return
an IP address (anymore).  So, when it does a lookup only once it should issue an error message about that server,
and proceed its startup as if that server was never there in the configuration.  When it is resolving DNS names on
a regular basis (e.g. once per day), it could keep the server configuration and keep retrying the DNS lookup at
that same interval and start using the server when the DNS lookup succeeds.
Not starting the service at all is only an option when all the DNS lookups have failed (i.e. there is no server) and
there is no mechanism to re-try the lookups.  When there is, it is much better to keep the service running.
(after all, a network may not be available at boot time and may become available later)

I find this statement of behavior (treat NOSERV/NXDOMAIN as an excuse to forget a server/peer/pool) a bit astonishing, and very un-Unix-like.

Read it again please.  When there IS a retry mechanism, it should not drop the server.  When there isn't, it should not
completely exit but only drop the server that cannot be looked up.

Rob


--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble?  Email listmaster@xxxxxxxxxxxxxxxxxxxx.


Mail converted by MHonArc 2.6.19+ http://listengine.tuxfamily.org/