As a side note I do not see that error for that domain. I get an A record which belongs to Cloudflare. Cloudflare could just as easily drop that domain into an account that displays the censored error message as text/plain to the user and close the connection.
streameast.app. 282 IN A 172.64.80.1
it's not as if that's hard. unfortunately chrome has sat on this for years. dunno about other browsers.
Of course CloudFlare hijacking the domain and sending traffic to a page they host isn't a great solution either...
in no way supporting the act itself of dns blocking
- yes, the error has to bubble up to the user. i'm surprised the browser doesn't do this. i imagined EDE was plumbed into the browser becuase yeah -- no value for this otherwise and with PDNS we need such plumbing
- no, cloudflare does not hijack. they implement the court order for domains already under their management. this is no more hijacking than altering the DNS reply is hijacking, in fact less so since they only touch domains that they already serve. (BTW i am very much anti-cloudflare.)
Writing a follow up post is certainly valuable for raising awareness to anyone who had already read the original erroneous article.