[EMAIL PROTECTED] wrote on 6-3-2008 7:43:
Ahhhh, now I see :-)
Thanks
/Claus/
hi Claus,
FYI, the NTP pool introduced a geolocation DNS system a few months ago,
mainly because of load distribution problems in the european pool zones.
This explains why you see nearby servers, even when using world wide
pool zones (including vendor zones like pfsense.pool.ntp.org).
[EMAIL PROTECTED] wrote on 6-3-2008 6:23:
What I see is that my pfSense talks to a number of different time
servers
OpenNTPd, which is used as time client on pfSense, has the ability to
extract more than one server from a DNS record. The NTP pool DNS system
supplies up to five servers in a DNS record.
and many of those looks like ordinary ADSL subscribers which
scares me a little.
Maybe you object to time servers on an ADSL connection because of the
asymmetric latency of such a connection (which is not good for NTP
accuracy)? Note that if you're on an ADSL connection yourself, that
effect is canceled out, partly restoring your accuracy.
Also note that OpenNTPd is not the time client with ultimate accuracy,
so it's probably not an issue.
If you need more accuracy than your pfSense box can give, you would need
to run ntpd on a dedicated box (and maybe even you would want to be a
pool member).
I know your questions were already answered, but maybe this clarifies a
bit more.
regards,
Jan Hoevers
