Thanks again!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...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
- 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)
Yes I had checked all that.
I learned something about this mdns4_minimal addition to nsswitch.conf but as I'm not using a *.local domain internally I don't think it's relevant.
Note that systemd-timesyncd works on an old Pi still running buster (which I plan to replace), just not on this system.
For the record my local DNS server is a pi-hole (running on a separate system, not the Pi).
So, I changed to chronyd just now and it syncs on boot when configured to use to my local ntp servers by CNAME. Perfect!
Statistics: Posted by Legendary Rye — Sun Jan 12, 2025 6:32 am