Not an answer, but more information: I have a similar configuration using my own DNS server (named/bind9) and an ntp server using chrony. Both my ntp server and DNS server are running on the same Pi5.
When I start a system using systemd-timesyncd configured to use my ntp server it takes slightly more than 30 seconds for systemd-timesyncd to sync the time. This seems extraordinarily long to me (color me impatient!) I've never investigated why. I just did a test with systemd-timesyncd configured to use the ntp server FQDN and it takes exactly the same amount of time as using an IP address. Both (IP address or FQDN) are configured using my own timesyncd.conf in /etc/systemd/timesyncd.conf.d
With chrony, I have my clients configured with the ntp server FQDN, but also "iburst", and the system time is synced in less than 10 seconds.
So, as you might guess, all my production systems are configured to use chrony. However, I'm also impatient when I'm building a quick-test system, so rather than waiting for those extra few seconds to install chrony I use systemd-timesyncd where I unfortunately pay the price waiting those extra 20 seconds for systemd-timesyncd during the first boot of the system. (moral: nothing is free![:lol:]( "Laughing")
)
Based on my testing I'd say that something is a bit awry with your DNS configuration, but without further details I can't offer any useful suggestions.
When I start a system using systemd-timesyncd configured to use my ntp server it takes slightly more than 30 seconds for systemd-timesyncd to sync the time. This seems extraordinarily long to me (color me impatient!) I've never investigated why. I just did a test with systemd-timesyncd configured to use the ntp server FQDN and it takes exactly the same amount of time as using an IP address. Both (IP address or FQDN) are configured using my own timesyncd.conf in /etc/systemd/timesyncd.conf.d
With chrony, I have my clients configured with the ntp server FQDN, but also "iburst", and the system time is synced in less than 10 seconds.
So, as you might guess, all my production systems are configured to use chrony. However, I'm also impatient when I'm building a quick-test system, so rather than waiting for those extra few seconds to install chrony I use systemd-timesyncd where I unfortunately pay the price waiting those extra 20 seconds for systemd-timesyncd during the first boot of the system. (moral: nothing is free
)Based on my testing I'd say that something is a bit awry with your DNS configuration, but without further details I can't offer any useful suggestions.
Statistics: Posted by bls — Sun Jan 05, 2025 3:05 pm