[EMAIL PROTECTED] wrote on 22-9-2007 22:23: > On Sat, 22 Sep 2007, 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. > > Incorrect, the machines are OWNED by TT, not by their customers ! The > machines are on their OWN internal company network, NOT on their CUSTOMER > network. Like most providers do, TT does indeed already run its own ntp > servers, plenty of them.
How did you check who ownes those machines? ISPs have customers machines on their internal networks, that's called colocation, you can't tell the owner from the ip address. And it's unlikely even for a large ISP to run more than two or three ntp servers, there is no need. Even if we knew these machines were TT, there would be no justification. Redirecting large amounts of data to others by dns would be seen as a ddos attack. The pool wouldn't get away with it. Obviously you're angry with TT, maybe with good reason, but this is not the way to go. Jan _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
