Elektrine lite

← Feed

@iopq@lemmy.world

2026-11-08 15:04 UTC

I had them confused, CF is the target, not the proxy. The proxy would be another server, like SURF You can use your ISP’s IP for DNS and the Oracle proxy for the requests. SURF sees CF ODoH request for example.com CF sees an encrypted DoH request to SURF from your ISP’s address example.com sees a request from Oracle Oracle sees a request to the IP of example.com and encrypted packets from the ISP IP Cloudflare (now as host) gets a request from Oracle’s IP with ECH SNI pointing to example.com Nobody actually knows you went to example.com and not some other cloudflare site

Replies (1)

  • @hirihit640@sh.itjust.works 2026-11-09 08:13

    Based on my understanding of DoH and ODoH this doesn’t sound right at all. CF is a DoH provider. They receive DNS requests wrapped in HTTPS, they unwrap it and then resolve the DNS request, and send the response back wrapped in an HTTPS response. There are no other parties necessary. No ISP, no SURF, no Oracle. Besides, since CF unwraps the HTTPS request, CF already knows everything about the DNS request. Adding more parties just means more people know about the request. You can optionally add a proxy between you and the DoH provider (in this case CF). This is ODoH. This proxy can be an Oracle VPS. So in total there’s three parties: you -> Oracle -> CF. If Oracle and CF sell data to Google, then the DNS request gets tied back to you. If you have some resource explaining the packet flow that you are talking about, please link it.

    Open ##5551762