To clarify the terms that's encrypted DNS. DNS over HTTPS and DNS over TLS. 3 secure protocols (DNSCrypt is the best bur least supported)
Discussion
Very interesting. Would this be a one off for you or do you have other clients in similar setups?
Pricewise sounds a little expensive. But maybe it's the price for a one off client like me. It would be great if we could do half of that.
One off setup. I run a similar setup for myself. I'll think about it. The problem with the low price is that I need it to make sense for my time + the server cost (through nostr:nprofile1qqszdzu53dd2kjatpe2rpmjfu08lz9mkeuvrm7fmxg2el9nsa42pf9gpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsz9mhwden5te0wfjkccte9ec8y6tdv9kzumn9wshsma93a8)
Maybe 7500?
Otherwise you could set it up yourself, I'll share the docker compose config later tonught and you don't have to pay me or anyone else, except the server provider
It def makes sense for a one off thing. Though I was hoping I could help use or start a new provider for many folks here and get some sustainable number of clients to make it worth your time.
If I can get other people to sign up I would be willing to drop it to 2k sats, or less and even build a ui to purchase access to it
Nice! That could definitely get a lot of people interested. How would the resolver know if the user is a paying user, though?
Either a unique token per user. This is included in the sdns string for DNSCrypt
Or a user generated cert. Either choice works. And would be used for auth only and then dropped.
In fact now that I think about it more, the token could be a cashu token, so the payment and auth are the same process.