Description of problem: Currently, ntpdate.service is started before named.service during boot. When named is set up as the local DNS resolver, this causes ntpdate's first attempt to always fail with "can't find server" errors logged. To ensure that named starts first, ntpdate.service needs: After=nss-lookup.target I suspect ntpd.service should include the same change (and it's missing After=network.target, too). Version-Release number of selected component (if applicable): ntp-4.2.6p4-1.fc16
Should be fixed in ntp-4.2.6p5-5.fc18. Thanks. The ntpd service doesn't always need network or DNS (e.g. with a reference clock) and it's better to start it early so the clock frequency offset is set from the drift file.