Subject: Re: ntpd
To: None <email@example.com>
From: Christos Zoulas <firstname.lastname@example.org>
Date: 10/12/2005 22:18:50
In article <oqvf023020.fsf@castrovalva.Ivy.NET>,
Miles Nordin <carton@Ivy.NET> wrote:
>>>>>> "mn" == Miles Nordin <carton@Ivy.NET> writes:
> mn> so, that feature is not working. I checked FreeBSD, which is
> mn> also ntp 4.20, and it's broken over there, too.
>I checked a NetBSD 1.6.1_STABLE machine, which is ntpd 4.0.99i. The
>deferred name lookup feature _does_ work over there.
>I thought DNS was broken on that machine altogether, which was what I
>was vaguely remembering, but it turned out the real cause was:
>restrict default nomodify
>in /etc/ntp.conf which did indeed made 'server <hostname>' not work at
>all. I added 'restrict 127.0.0.1 #empty restrictions' and both
>nameservice and deferred nameservice retrying started working again on
>NetBSD 1.6. Adding the same line to NetBSD 3.0 doesn't help---you
>only get one shot at nameservice, at startup.
>I noticed some other regressions between 4.0.99i and 4.20. Here's the
> * ntpd_initres mechanism to keep trying failed DNS lookups broke
> * ntpq does not do reverse lookup for the 'refid' field at all.
> There was some changelog to stop lookup for fake refclock
> 127.127.x.x addresses, but it's not reverse-looking-up any
> * 'ntptime' no longer reports when ntp isn't working. For example,
> when ntpd is not running at all, a NetBSD 1.6 system reports:
You should file PR's with NetBSD and the ntp people...