undefined | Better HN

0 pointsjrochkind112y ago0 comments

Except there are an indefinite number of other DNS servers, free and with a contract, that Turkish users could use too, from an indefinite number of different vendors. It's a heck of a lot harder to block "any DNS server that isn't under Turkish government control" than it is to block twitter.

We can all speculate, but really I was hoping that someone had some additional information, perhaps because they are in Turkey, on what's going on exactly.

(Is it too much to expect discussion of technical details on HN, instead of political bickering? On anything involving Turkey, anywhere on the internet, yeah, it probably is. The reason why I'm curious about technical details is, of course, because I have an interest in knowing how to circumvent and help people circumvent whatever censors are up to these days).

0 comments

2 comments · 1 top-level

vacri12y ago· 1 in thread

I imagine that if you wanted to block all DNS queries not going to government DNS, you put a block on packets routing to port 53. This is going to hit a lot of businesses that use their own DNS systems though. It would be harder to do a wide-ranging-but-not-total block, methinks, but I am not a net admin; I don't know the feasibility of mass port blocking.

miopa12y ago

Mass port blocking is easy. Not so hard and less disruptive is DPI of all port 53 traffic, blocking only requests for Twitter. In addition, you block the IP address range of Twitter to foil the smart-asses who use hosts file.

j / k navigate · click thread line to collapse