TorrentFreak is wrong about Google DNS notification

The vast majority of people will not see EDE errors. Even when they are set there is no guarantee that downstream resolvers have it enabled. The default in Unbound is disabled and people rarely check logs. Even if someone is using DoH their browser would have to translate the specific text to the user if it received such an error. Here [1] are some notes on the support of EDE around the internet.<p>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&#x2F;plain to the user and close the connection.<p><pre><code> streameast.app. 282 IN A 172.64.80.1 </code></pre> [1] - <a href="https:&#x2F;&#x2F;blog.apnic.net&#x2F;2023&#x2F;09&#x2F;28&#x2F;extended-dns-errors-unlocking-the-full-potential-of-dns-troubleshooting&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blog.apnic.net&#x2F;2023&#x2F;09&#x2F;28&#x2F;extended-dns-errors-unlock...</a>

If the DNS error doesn&#x27;t bubble up to the eyes of the average user it might as well not exist, so torrentfreak isn&#x27;t wrong.<p>Of course CloudFlare hijacking the domain and sending traffic to a page they host isn&#x27;t a great solution either...

I use Google DNS over my isp only because I thought they didn&#x27;t involve in these shenanigans. Where to next?

There&#x27;s a box labelled &quot;Submit a correction or tip&quot; at the bottom of the original article. Filling that in might have been better time spent than writing a blog post.