Yeah, the problem is pihole-FTL starts a few seconds before NTP has set the system time. I did try the DELAY_STARTUP option, but that didn't work. Here are my log entries showing it did delay starting the resolver until NTP had set the time properly
[1969-12-31 18:01:01.477 1642M] Sleeping for 3 seconds as requested by configuration ..
[2021-03-27 06:24:06.702 1642M] Done sleeping, continuing startup of resolver...
but I still got the errors. DL6ER said it was because most of the startup is done before the delay is processed. There was a suggestion of moving the delay earlier, immediately after processing options file, but I don't think it went any further than just a suggestion. See this thread: getOverTimeID is too large warning - #8 by jfb