On Monday, February 25, 2013 at 0:04, Henk P. Penning wrote:
Maybe ntpd should, for each pool association, keep a timestamp
last seen in dns, and make decisions based on that ; like
maybe drop if not seen for 3 months.
Some zones have more than 500 servers, it's completely possible that you
ken...@kenyonralph.com said:
The pool command works great for me.
Thanks. I'm slightly surprised that nobody else has responded. If people
respond to me off-list, I'll summarize in a few days.
ken...@kenyonralph.com said:
Why would you do this? If the pool monitoring system reduces the
a...@ntppool.org said:
Is there a way to do that? I assume it would use DNS.
There isn't. I could setup a DNSBL-style zone to check is this server
still ok to use, but I don't think that's really what we need.
I was thinking of something like if you got 1.2.3.4 from de.pool.ntp.org you
