Platforms without a RTC need to do what we did last century to set the clock at boot. You have a clock file that is touched every minute and that file’s time is used to set the approximate time at boot. -- Mark Andrews
> On 22 Aug 2026, at 07:35, Danny Mayer <[email protected]> wrote: > > > On 8/21/26 3:05 PM, Colin Vidal wrote: >>>> Am 21.08.26 um 19:33 schrieb Colin Vidal: >>>>> This make the guess from my previous email more relevant. IIRC the >>>>> Raspberry Pi >>>>> doesn't have battery so they would lost clock after a power outage. >>> Yes, but it syncs via NTP - if the network connection is established. >>> Does that cause my issue? >> It's hard to tell without logs, but it is a possibility. (Also keep in mind >> that NTP needs to lookup a name to contact the servers. This might be a >> chicken-and-egg problem if the machine's resolver is itself.) > > Yes it's definitely a chicken and egg problem. When NTP starts up it needs to > perform a DNS lookup for the addresses of the NTP servers so how it does that > depends on how you have set up your NTP and DNS environments. > > Until you have a good time you won't be able to validate any Certs. > > Danny > Network Time Foundation > > > -- > Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from > this list. -- Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list.
