Raspberry Pi OS • Re: systemd-timesyncd fails sync time for minutes after boot - possible DNS problem?

I'm inclined to dump systemd-timesyncd and just use chronyd. I suspect there's some edge-case bug in it but I'm unwilling to spend my leasure time teasing it out.

Can't blame you...as I mentioned chronyd works well.

I'd be inclined to do more sleuthing, but that's just me. You've probably already done all of this, but just in case...

• Is the DNS server accessible to systemd-timesyncd when you think it is? (you could run a test service right before systemd-timesyncd to eval)
• Does the DNS name resolve as you think it should? (guessing it does, but just for completeness...)
• Are your DNS server and resolv.conf fully configured for your domain? Is there a 'search' command in resolv.conf? (They probably are, but again...completeness)

Other than that, I'm fresh out of ideas without a lot more info about your DNS server, the .nmconnection on this annoying system, etc etc

Statistics: Posted by bls — Sun Jan 12, 2025 12:35 am

---