> On 5 Jan 2018, at 11:10, Karl Palsson wrote:
>
>
> The freshly released busybox 1.28 has a number of DNS related
> fixes for NTP btw.
>
> ntpd: do run the script at least once in 11 minutes
> ntpd: improve treatment of DNS resolution failures
> ntpd: mention in help text that
Kevin Darbyshire-Bryant wrote:
>
> I don’t have a magic patch for this problem. It seems to me
> that ideally busybox ntpd shouldn’t serve time until it has
> sync’d. A horrible hack idea: firewall rule to drop incoming
> ntp requests from clients… have an ntpd hotplug script that
> captures the
> On 5 Jan 2018, at 08:22, e9hack wrote:
>
> Am 02.01.2018 um 16:29 schrieb Kevin Darbyshire-Bryant:
>> Move 'check dnssec timestamp enable' from SIGHUP handler to SIGUSR2.
>
> Hi,
>
> your patch fixes the DNS problem for me.
Good, as I suspected it would.
>
> Now I get another ugly behaviou
Am 02.01.2018 um 16:29 schrieb Kevin Darbyshire-Bryant:
> Move 'check dnssec timestamp enable' from SIGHUP handler to SIGUSR2.
Hi,
your patch fixes the DNS problem for me.
Now I get another ugly behaviour which is more related to ntpd from busybox.
Ntpd answers to ntp request before it did
upda
