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
Harlan is getting ready to release the next version of the standard NTP
package. The pool command seems to work. How many of you are testing it?
I think clients using the pool should occasionally check to see if an address
they picked is still in the pool and pick another one if it has
On 2013-02-24T17:30:01-0800, Hal Murray hmur...@megapathdsl.net wrote:
Harlan is getting ready to release the next version of the standard NTP
package. The pool command seems to work. How many of you are testing it?
The pool command works great for me.
I think clients using the pool should
On Sunday, February 24, 2013 at 17:30, Hal Murray wrote:
Harlan is getting ready to release the next version of the standard NTP
package.
Great!
The pool command seems to work. How many of you are testing it?
I think clients using the pool should occasionally check to see if an address
