Earlier quoted context omitted.
It means you can use a decently fast DNS server like Cloudflare without the major privacy problems of using Cloudflare. Or DNS4EU, or any non-ISP DNS server really. Your ISP snooping on you with SNI logging is something people using normal ISPs don't need to worry about, but feeding all your data into a profit-driven company is.
> something people using normal ISPs don't need to worry about It doesn't matter which ISP you're using if the cables are tapped, which they pretty much are.
Show HN: Running the second public ODoH relay
21–30 of 50 posts
Re: Show HN: Running the second public ODoH relay
#22Re: Show HN: Running the second public ODoH relay
#23Re: Show HN: Running the second public ODoH relay
#24What’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?
Re: Show HN: Running the second public ODoH relay
#25What’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?
My, admittedly cynical, view of it is that the main selling point is that you share your data with the person running the ODoH server. The truth is that very very few people run their own recursive nameserver. The entirely reasonable assumption for any authoritative nameserver, like .com, is that the query is being asked on behalf of someone else and knowing that a user of your nameserver asked for the ip of sexyshee…
Re: Show HN: Running the second public ODoH relay
#26Me 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 WilderRe: Show HN: Running the second public ODoH relay
#27What is the end-game for the private TLD? Is this going to turn into some cryptocurrency thing?
Re: Show HN: Running the second public ODoH relay
#28Re: Show HN: Running the second public ODoH relay
#29anyone know how the diagram was made? pretty cool.