I am using ntp-client to set the system clock on a Raspberry Pi. The network connection is via wireless. The initscript for ntp-client starts before the network has finished authenticating with the access point (using wpa_supplicant). Changing the initscript for ntp-client to list "need net" instead of "after net" resolves this issue for me, as ntp-client then waits.
This was probably already in https://bugs.gentoo.org/show_bug.cgi?id=439564 fixed
This is an issue on all my systems which use NetworkManager. Having "after net" in the ntp-client init script makes ntp-client start immediatelly after NetworkManager has started, but before it established a network connection (authentication, DHCP, ...).
Consequently it fails due to DNS resolve errors or the like.
Changing the init script to "need net" makes ntp-client wait until the whole connection is established and solves this issue for me.
Please consider SpanKYs comment in https://bugs.gentoo.org/show_bug.cgi?id=439564#c3 and the obvious difference in behaviour between "need net" and "after net". I ask you to consider changing it back to "need net".
Same problem on my system after updating to newer hardware (not sure if the different network card has triggered it or the fact that the new system is just so much faster due to the ssd).
"need net" instead of "after net" solved it for me. Thanks for the hint!
"need net" instead of "after net" fixes it. Please fix it upstream.
*** This bug has been marked as a duplicate of bug 439564 ***