I hope you're not getting annoyed with me!
Another idea occurred to me just now, after finding I may
have had my IP address blocked by a server because it thinks I was being abusive. I accidentally had the same NTP server listed twice in ServFile.txt
, with one other server in between:some.ntpserver.com
I can no longer access "some.ntpserver.com", so I'm wondering if it didn't like that I was checking it so repeatedly.
I'm only making an assumption, and I am not
asking you what happened. I'm just framing the feature suggestion: A "Scan for duplicates" function!
In my opinion, it's a good idea (generally speaking) to remove dupes, even if you don't get banned.[slightly crazy mode]
A basic duplicate-finding function would be really nice, but what would also be really neat is a "DNS duplicate" function. That is, resolve each domain-baesd entry in the list, and flag as a duplicate any matching entry that is listed as an IP address. For example, let's say you have this in your list:some.ntpserver.com
It doesn't look like a standard dupe, but since "some.ntpserver.com" resolves to "126.96.36.199" (in this example), it's a duplicate, even though the strings aren't equal... Hence, "DNS duplicates". (I'm really tired, so I'm sure there is a better name for it than "DNS duplicates"...)[/slightly crazy mode]
OK, before you read on (if you still are...), please understand that I'm not trying to find ways to take up your time and efforts. I'm just throwing this out there because you have a really good attitude and an open mind, not to mention programming skill. I never call these things "requests". I mean them as "ideas" or "suggestions".
On that note, yet another idea: NTP server statistics. I have a pretty big server list, and there are a few servers that time out sometimes, but not all the time. If I could see stats on the servers, I'd know if it was worth keeping these servers in the list. For example, if a server timed out 90% of the time, it's gone. If it timed out 10% of the time, we'll put up with it. (It would be even better if iTimeSync could automatically skip servers that had a bad track record.)
In any case, thanks for reading.