On Mon, Mar 08, 2010 at 03:03:39PM +0500, ???? ??????? wrote:
> Mar 6 20:28:25 r1n0 ntpd[29340]: 1 out of 2 peers valid
> Mar 6 20:28:25 r1n0 ntpd[29340]: bad peer from pool pool.ntp.org (not
> resolved)
> Mar 7 15:01:02 r1n0 ntpd[4230]: 0 out of 2 peers valid
> Mar 7 15:01:02 r1n0 ntpd[4230]: bad peer 192.168.0.3 (192.168.0.3)
> Mar 7 15:01:02 r1n0 ntpd[4230]: bad peer from pool pool.ntp.org (not
> resolved)
>
>
> due to unknown reason pool.ntp.org was not resolved during ntpd
> startup (named is run on the same machine), after some time name can
> be easily resolved.
>
> .... will ntpd try to resolve it later or will it give up ?
>
> Cheers,
> Ilya Shipitsin
It should recover from temporary nameserver problems.
-Otto
