Besides that, DNS queries to all servers are blocked if you try to get a blocked site's IP. No hijacking attempt here, as far as I can see.
I routed only Wikipedia through TOR with a browser extension. With this setup not all DNS queries goes through proxy. So I had to take advantage of CoreDNS' dns-over-tls support.
Because people who knows basic networking and also read English are less than a thousandth of the country, their method works very well enough.
Wait, so if I was in Turkey, a request for wikipedia.org to my ISP DNS server would not only have failed, but caused all my other queries to fail as well? For how long?
If you just suddenly disappeared without a note, that's one thing. "Please stop action X occurring on your network" sounds very clear and direct.
Edit: I see I'm getting downvoted here but I want to explain why I am passionate about this topic. As someone who supports network infrastructure and it's operation I'm on the hook to find out why x can't talk to y. It's a challenge when dealing with ISP/country level blocks or packet manipulation. Proving that this is something deliberate versus a legitimate broken thing is a process to go through. Not being able to tell a customer why is not a great story. Different countries have different techniques for this and over time you learn them. Seeing your packets in a traceroute going to a hop that has a DNS PTR record that says "DPI" in the name is a nice heads up to an operator to give you that sort of indication of what you're dealing with. I am aware that basically no country publishes such blocks today and ISPs that are forced to implement such blocks are usually instructed to not tell you anything about it (sometimes off the record, if you're lucky).
It's not about offense in the parent comment, it's about theft.
I see this as a reasonable response, given no additional context.