The simplest solution seems to be to cache a lookup of pool.ntp.org. It would only need to be used if the normal DNS target for ntpdate fails. Once time is set, we can update the cached values of the pool once again (if they've changed).

--
David P.



On Sun, Mar 23, 2014 at 7:15 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
Aaron Wood <woody77@gmail.com> writes:

> or we find a way to have long-lived dnssec entries.

Is the timing controllable somehow? I.e. would it be possible to set up
a special domain name with a really long-lived key that could be queried
indefinitely for the IP address of one or more NTP servers, even in the
face of an a wrong clock?

-Toke

_______________________________________________
Cerowrt-devel mailing list
Cerowrt-devel@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/cerowrt-devel