Mouse wrote:
I find it interesting that the misbehaviour stopped almost immediately upon my stopping NTP service on that address. (It would be difficult for me to tell how promptly NTP traffic stopped.)
I think this can be well explained by the fact that the misbehaviour is not from users of ntpd but only from users of different crappy NTP implementations that usually in fact are more like SNTP and do things like issuing a DNS lookup for every time sync, have very short uptimes, and have no possibility for manual configuration. When you leave the pool and your DNS entry is gone, they very soon have no way to find you anymore. I left the pool on IPv4 more than 5 years ago, but I still see clients polling my server even though it has changed IP address. Apparently it has been hardwired in some ntpd config files at that time by getting my IP address from a pool.ntp.org lookup, getting the reverse, and writing that hostname in ntp.conf. Rob _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
