Eugene Smiley wrote on 22-9-2007 16:39: > Jan Hoevers wrote: > > [EMAIL PROTECTED] wrote on 22-9-2007 12:42: > >> An easy way to solve the TT problem and the like would be to configure the > >> pool DNS so when it gets a query from the 88.245.0.0 - 88.245.255.255 IP > >> range, the pool DNS would then return the IP of one of the numerous ntpd > >> servers that TT is running on their OWN network. Problem solved ! No more > >> TT traffic for pool members ! > > > > That would not solve any problem, it would redirect it to TT customers. > > Come on! This would be a deliberate attack. > > Actually the server point to other servers in private IP space (192.168..) If > these were customers they'd likely point to different sources. These can't > possibly be customer resources.
May well be colo customers, there's no way to tell. And how did you check those 192.168.. addresses are TT's own machines? Maybe they're colocated too. Anyway, bouncing a problem back to its supposed source would widely be seen as an attack. Also consider there's probably no malicious intent from TTs side. There were many examples in the past where this kind of warfare just caused more trouble. The pool DNS system could deny service to TT addresses, but I suppose that has been considered months ago. Jan _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
