My plan is to just enable records for 2.pool.ntp.org (and
2.fedora.pool.ntp.org etc) and see how that goes. Depending on the
outcome, we can make a ipv6.pool.ntp.org IPv6-enabled or IPv6-only
pool.
For the use case I envision (production-style support for v6-only
hosts), it doesn't
Any idea why 2.us.pool.ntp.org is resolving records, but
[13].us.pool.ntp.org is not (nor, for that matter, almost any other set of
hosts I try)?
On Mon, Jun 06, 2011 at 05:14:51PM -0700, Ask Bjørn Hansen wrote:
Hi everyone,
If you add 2.beta.grundclock.com to your ntpd.conf and you
On Jun 7, 2011, at 1:38, Tim Bray wrote:
On 07/06/11 04:43, Anssi Johansson wrote:
My only concern at this time is that it's going to take about 18 hours to
get my IPv6 NTP servers' score from -9.8 to the acceptable score of 10.
There's still about 20.5 hours to go until June 8th 00:00
On Jun 7, 2011, at 1:51 AM, Rob Janssen wrote:
You almost certainly don't want to be implementing stateful rules for NTP
traffic; you'll fill up the state table with lots of entries for no benefit,
as UDP isn't stateful.
Just pass UDP 123 and ephemeral high ports in both directions.
