At first glance, the Mozilla Policy Requirements for DNS over HTTPs Partners look pretty good:

It's worth reminding the sceptics out there, that the resolvers we are using today have committed to no such standard of operations. Quite the opposite, in fact.

The only item I have doubts about, is the public list of blocked domains. I don't think creating a public list of pedo sites is at all smart. I wonder if a list of hashed domain names would suffice instead?

I wonder what sort of business case can be made for operating a public DoH resolver?

The main problem with the DoH concept, is centralization of traffic - everyone sending all their queries to CloudFlare or Google.

Having a clear way to make money providing this service, would make it easier for geeks like me to pitch to our employers.

The only obvious business case I can think of is opt-in censorship: Filtering DNS queries to make people (parents, businesses) feel safe. 🙄

@HerraBRE Why do we need a business case? What is the business case with Linux? With Wikipedia? With Mastodon? With the instance you use?

@bortzmeyer @HerraBRE there are multiple business cases for Linux. Most contributors to the kernel nowadays are paid specifically for that. Open access/free software/etc. is not antinomic with business.

@hugo @HerraBRE But Linux was working and was used long before this happened. And see my other examples (what is the business case for a Mastodon instance?)


@bortzmeyer @hugo @HerraBRE technically working and becoming relevant on a global scale are different things.

Sign in to participate in the conversation

Generalistic and moderated instance. All opinions are welcome, but hate speeches are prohibited. Users who don't respect rules will be silenced or suspended, depending on the violation severity.