RuudBurger/CouchPotato — comment on commit 41e89a3396aa050ee54a1aeab53f55f85d0e82cf
File:  line 0
By stup2p:

It's a bad idea. This problem only affects users of a couple ISPs in Belgium. The problem began because the BAPF can get the Belgian courts to force Belgian companies to block DNS queries for such domains. The response here in this patch is to have your all your users in the entire world rely on a Belgian company (dns.be) for resolving tpb domains. That is totally backward, having everyone count on one of the few DNS providers least resilient to this censorship. You're committing your entire user base to a game of DNS whack-a-mole for the sake of a very small minority who have other simple workarounds at their disposal.

If you're going to address this problem at all, it should be by allowing configurability of the hostname used instead of hard-coding them. If we do continue hard-coding them, the last domain name in the world we'd want to use would be one with a DNS SOA in Belgium.