SaaS Metrics
Show HN: Running the second public ODoH relay
Expanding the ODoH ecosystem by providing an alternative public relay, addressing the lack of account-free, privacy-focused DNS options.
View Origin LinkProduct Positioning & Context
AI Executive Synthesis
Expanding the ODoH ecosystem by providing an alternative public relay, addressing the lack of account-free, privacy-focused DNS options.
The market for privacy-focused DNS is dominated by services requiring user accounts, creating a friction point for users prioritizing anonymity and simplicity. ODoH (Oblivious DNS-over-HTTPS) offers a critical alternative by eliminating account requirements, yet its adoption is hindered by a scarcity of public relays. The introduction of a second public ODoH relay directly addresses this infrastructure gap, enhancing the protocol's viability and accessibility. This development signals a growing demand for truly anonymous internet infrastructure and decentralization in core services like DNS. For B2B SaaS, this trend suggests opportunities in providing robust, account-free privacy solutions or contributing to open protocols that reduce vendor lock-in and enhance user trust.
Every privacy-focused DNS service requires an account: NextDNS, Cloudflare for Families, Apple's iCloud Private Relay (paid, iOS-only). The protocol that doesn’t require one - ODoH - had basically one well-known public relay operator (Frank Denis on Fastly Compute, default in dnscrypt-proxy). I built a second one and the client to talk to it.
Related Ecosystem & Alternatives
Discover adjacent products, open-source repositories, and developer tools sharing similar technical architecture.
Deep-Dive FAQs
What is Running the second public ODoH relay?
Running the second public ODoH relay is analyzed by our AI as: Expanding the ODoH ecosystem by providing an alternative public relay, addressing the lack of account-free, privacy-focused DNS options.. It focuses on The market for privacy-focused DNS is dominated by services requiring user accounts, creating a friction point for users prioritizing anonymity and...
Where did Running the second public ODoH relay originate?
Data for Running the second public ODoH relay was aggregated directly from the Hacker News community ecosystem, representing raw developer and early-adopter sentiment.
When was Running the second public ODoH relay publicly launched?
The initial public indexing or launch date for Running the second public ODoH relay within our tracked developer communities was recorded on May 14, 2026.
How popular is Running the second public ODoH relay?
Running the second public ODoH relay has achieved measurable traction, logging over 88 traction score and facilitating 26 recorded discussions or engagements.
Which technical categories define Running the second public ODoH relay?
Based on metadata extraction, Running the second public ODoH relay is categorized under topics such as: privacy-focused DNS service, ODoH relay, protocol, Fastly Compute.
What are some commercial alternatives to Running the second public ODoH relay?
Our semantic intelligence engine identifies potential commercial alternatives in the SaaS space, such as Brew , which offers overlapping value propositions.
How does the creator describe Running the second public ODoH relay?
The original author or development team describes the product as follows: "Every privacy-focused DNS service requires an account: NextDNS, Cloudflare for Families, Apple's iCloud Private Relay (paid, iOS-only). The protocol that doesn’t require one - ODoH - had basically ..."
Community Voice & Feedback
Pretty cool to see someone actually running public ODoH infra instead of just talking about privacy in theory. I'm just wondering what the biggest operational pain has been so far running a public relay.
anyone know how the diagram was made? pretty cool.
To me this feels like turtles all the way down. Ultimately who owns and controls the layer-4 proxies and DoH servers matters and can easily get into turtle arguments. Who controls the certs controls the mathematical obfuscation (encryption) also matters. Pieces of the puzzle can be shared and recombined at any time.Me personally, I will stick with running my own DoH servers and thus I need not run any turtles (layer 4 proxies) in the middle of my already encrypted connections. Anyone running Unbound DNS can enable DoH if Unbound was built including '--with-libnghttp2' which the Alpine Linux version has. At the moment my browser is talking to Unbound over DoH on my local network so I get the advantages of ECN but I can easily switch it to any server where I have installed Unbound. Ultimately DNS at some point will be unencrypted UDP port 53 so I would rather it be me that determines where that happens so I can optimize my own cache and pre-cache cron jobs to mask my DNS behavior, but that's just me. Others can do whatever they want, as they should. The people that operate my ISP are bigger deviants than I and they know that I know that they know that I know this.Oh and as a funny side note, I can warm up cache on entirely unrelated nodes and then transfer the cache export to any node and keep it valid on that node as long as I wish making the vast majority of my DNS requests respond in less than 700 nanoseconds not that I am in any hurry. unbound-control dump_cache | bzip -9c > /dev/shm/dump_node_1045.txt.bz2
I can then bring those cache dumps in from any node to my home network making DNS resolution entirely invisible. Automation is only limited to ones imagination. Or AI's imagination. I personally find it beneficial to listen to Pure Imagination from Willy Wonka & The Chocolate Factory (1971) RIP Gene Wilder
I can then bring those cache dumps in from any node to my home network making DNS resolution entirely invisible. Automation is only limited to ones imagination. Or AI's imagination. I personally find it beneficial to listen to Pure Imagination from Willy Wonka & The Chocolate Factory (1971) RIP Gene Wilder
What is the end-game for the private TLD? Is this going to turn into some cryptocurrency thing?
[dead]
[flagged]
[dead]
What would it take to get truly anonymous dns? I guess it’s not really possible no?
What’s the selling point of ODoH given the low uptake of ECH which means the name of the server you’re talking to is given away anyway?
The relay is a systemd unit on a VPS, Caddy for TLS, SSRF-hardened (regex-strict hostnames, no IP literals). eTLD+1 same-operator check rejects relay+target run by the same org by default. HPKE is odoh-rs from Cloudflare```
cargo install numa# set mode = "odoh" in numa.toml
```Repo: https://github.com/razvandimescu/numa
cargo install numa# set mode = "odoh" in numa.toml
```Repo: https://github.com/razvandimescu/numa
Discovery Source
Hacker News Aggregated via automated community intelligence tracking.
Tech Stack Dependencies
No direct open-source NPM package mentions detected in the product documentation.
Media Tractions & Mentions
No mainstream media stories specifically mentioning this product name have been intercepted yet.
Deep Research & Science
No direct peer-reviewed scientific literature matched with this product's architecture.