[Arm-dev] Chronyd alternative - Re: So is this a bug to report - Re: Re: Re: System time

[Robert Moskowitz]

On 09/02/2015 11:12 AM, R P Herrold wrote:
> On Wed, 2 Sep 2015, Robert Moskowitz wrote:
>
>> This is not working on a new mSD with only chrony installed and the changes
>> listed below.
>>
>> It works on F22 'out of the box' with these changes.
>>
>> Got to get this working...
> I looked and tested when you posted a similar complaint
> yesterday, as to polling from an ntp pool.  The DNS lookups
> for
> the servers to use from the pool were markedly longer (0.8+
> sec) than customary lookups.  Doing it manually, what timings
> (non-cached at the providing nameserver -0- may take some
> manual cache flushing) for lookups of hostnames, are you
> seeing?

Russ,

I really do not have the experience with the various tools to answer 
that question.

that bind ws running and could resolve some fqdns, but failed on the 
centos ntp pool fqdn.  If I manually set the time with the 'date' 
command, then those lookups work.  This indicates that there is 
something in the response that my system, with its bad date/time did not 
like (too far in the future?).  But why was it ok with other look ups?

So I see two ways to 'fix' this.

Even though this system is a nameserver, put a second DNS being my ISP's 
DNS server.  Then MAYBE it will work (have not tested this yet, if this 
is a time/stamp issue the 1st, ie localhost, DNS response should still 
fail).

Get chrony to set the time based on the last boot time.  I have this 
working on F22, but not on C7.  So it SHOULD be a config problem...