named and ntpd start order in rc.d

Nerius Landys nlandys at
Wed Dec 3 15:38:58 PST 2008

> When ntpd first starts up, it forks a child process to perform DNS
> resolution of the timeservers listed in its config.  If that fails, that
> generally indicates that DNS was not working at the time, or something else
> was going wrong with the network.
> [ See ntpd/ntp_config.c, search for fork() or "ntpd_initres". ]
> The fix is to make sure that you have a working network and resolver
> available when you try to startup ntpd.  Failing that, you can hardcode IP
> addresses in /etc/ntp.conf, but that's a bad idea for anything outside of
> timeservers which you control.

Thank you!  That explains the problem.  I had a hunch that the problem
was along these lines.

More information about the freebsd-questions mailing list