Dave Hart wrote: > Danny Mayer wrote: >> Dave Hart wrote: >>> Harlan Stenn wrote: >>>> A single "pool FOO.pool.ntp.org iburst" line should be >>>> enough. >>> ... assuming you're using 4.2.7. Â With 4.2.6 or earlier, >>> "pool" spins up only one association, and uses DNS only >>> at startup.
Server only does one, pool does as many as IPs are returned in the DNS query? >> That didn't used to be true, at least in the original >> code that was in 4.2.5 which would create up to 10 >> associations depending on the number of IP addresses >> returned by the DNS resolver and how many previous >> associations had been set up. Did something change >> in 4.2.6 to break that? > > No, thanks, good point. I simply misremembered the > old behavior. As Danny said, the old pool implementation > would spin up as many associations as the DNS query > returned addresses, capped at maxclock (default 10). > However, pool.ntp.org changed its behavior in response, > reducing the number of addresses returned per query, > on the flawed theory that pool users don't need more > than three servers. So with 4.2.6 and earlier using > *.pool.ntp.org, each "pool" directive spins up 3 > associations. Earlier versions, yes, however many IPs are returned by the pool query (usually 3). However pool in.pool.ntp.org only returns 2 IPs per query, unlike (most ?) other zones. I don't know why, I would guess due to less total servers available in that zone? -- E-Mail Sent to this address <[email protected]> will be added to the BlackLists. _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
