Let's take the case that it's a local machine - on your local network - acting as the ODNS Stub. The DNS request is then encrypted from your machine to the tru

Let's take the case that it's a local machine - on your local network - acting as the ODNS Stub. The DNS request is then encrypted from your machine to the trusted ODNS Stub - but then from that ODNS Stub out to some resolver on the internet, there exists the DNS query (whether encrypted or unencrypted) - sourced from your same public IP that your machine would have sourced it from in the first place, correct? I'm certain I don't understand the entirety of ODNS - but the basics still have to exist - something still needs to make a query on behalf of the initial user to some authoritative server (unless the answer is already cached). I guess, what I'm picturing in this case, is that if the trusted resource (ODNS Stub) exists in your local infrastructure, then the source outgoing to the internet might as well just be your local machine in the first place - because that's how 'the internet' sees it anyway. Anyway, I'm all for making DNS more secure...and this seems to be one way to change where your trust lies, but not a definitive solution, to me.