[Pool] Taking down my NTP server in Turkey
mouse at Rodents-Montreal.ORG
Wed Aug 1 17:24:29 UTC 2012
>> First, did anybody try to contact Turk Telekom regarding this
>> behavior of their CPE? [...]
> Several attempts have been made in the past, [...]. None have
> resulted in any improvements in the ntp behaviour in those routers.
They're using the tr country-code zone? Then I have to wonder why we
still have a tr zone. As *ahem* unfortunate as it would be for other
Turks, it appears Turk Telekom is uninterested in participating in the
cooperative, mutually helpful network the pool is designed for.
Putting up an announcement on (sigh) the pool webpages that we have no
tr zone (and perhaps giving some subtitute, tr2 maybe?) and explaining
why would, it seems to me, break the abusive access while being about
as minimally disruptive as possible to others.
But this seems so obvious I can hardly imagine nobody's thought of it
before. So presumably there's some reason why it hasn't been done. Is
it just that pool management disagrees with me that breaking the abuse
is worth the disruption it would entail for other Turks? Or is there
something else going on?
If it's a question of the DNS servers getting hammered if they return
NXDOMAIN, perhaps they could instead return an address of 127.0.0.1 (or
maybe 127.0.0.2 or some such) with a very long TTL? Or perhaps the
addresses of Turk Telekom's customer-facing NTP servers, if they have
any and their IPs are known?
/~\ The ASCII Mouse
\ / Ribbon Campaign
X Against HTML mouse at rodents-montreal.org
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B
More information about the pool