Hi, since the pool servers are monitored anyways: May it be a good idea give negative scores for servers with really bad configuration issues (but which are working as a time reference)?
So i.e. servers with open monitoring could get removed from the DNS after a week if the configuration won't be fixed. I think, people may not react on simple mails or warning messages (in fact, I log in to the pool website only once a month....) if the server is working for them. Maybe I'm wrong with it, but I see how many open DNS resolvers are out there besides the fact that there are enough informations and warnings. Greetings from Wuppertal Max Am 30.12.2013 23:17, schrieb Brian Rak: > I think part of your diff got cut off. That text looks good to me though. > > Scanning pool servers to see who was vulnerable was going to be my next > question :) That seems like it would be a good check to have when > someone goes to initially add a server. It's pretty quick to do, and > would get them to fix it when they're already looking at the NTP config. _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
