> definition it doesn't matter anyway. Noone sells NTP as a service (?) so
Actually many ISP's include ntp service; look for a host named "time" or "provider" in their .net domain, possibly after doing a traceroute and trying the nearest router or two first (since many routers support serving "broadcast" ntp, for the use of configuration-free clients.) The "insane-clock" stuff is quite useful; one thing to watch out for instead is that you don't peer with *inside* machines if you are concerned with the "ntpdc -c peers <hostname>" function actually finding out about them (this is more paranoia than security, but I thought it was worth pointing out.)
