On 23-02-17 18:36, Rob Janssen wrote: > Tim Bray wrote: >> On 23/02/17 10:38, Rob Janssen wrote: >>> It depends on where the routing problems actually are. When the >>> problem is in some >>> transatlantic link, there is no issue for the server to be in European >>> pools.
Usually it is not the transatlantic link link, but the (temporary) filtering policies of a network company that operates at both sides of the transatlantic link. I remember a situation in the UK, where one system with upstream to company A could not connect to an NTP server with upstream company B. Situations where both client and server were routed through upstream A only worked fine. The same was true for client servers via upstream B only. Networks do not follow the borders of the country (in most countries...) >> Well, lets say you host a website. This website pays your bills. >> >> You have 1 monitoring system, and it says your website is down sometimes. >> >> So you blame the monitoring system, and install a second monitoring >> system on another ISP. This always reports site up. >> >> So you say `My website is up if either monitoring system thinks it is up`. >> >> Well, then you are wrong, because actually what you are saying is. >> `My website is up for half the internet, and down for half the >> internet` For most people, that is a problem. Some people can't get >> to your website. >> >> Does this apply to the pool? > > NO > For NTP pool servers it is perfectly fine when they are reachable for half the > internet, and provided only to that half. The only problem you have to solve is: how does the DNS system know to which half they can serve your IP? Arnold _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
