DNS requests exposed to ISP about dns HOT 3 CLOSED

That is the correct behavior. For the first question, you will need to run the docker image in your home network lets say on a raspberry pi at ip 192.168.1.10 port 53. Then you can configure your router to use this dns server.

For the OpenVPN question, you just need to run the docker image on the server, configure it to be accessible from clients, then make it the default dns server.

The key is that the routing to the docker image should not leave your network since its just plain unencrypted dns queries.

from dns.

Ah thanks that makes a lot more sense. I thought the use case was a cloud hosted dns server.

(I was struggling before to understand in your diagramme why the dns servers request went back through the router to cloudflare - but now viewing it as a local network it makes sense).

Am I correct in thinking that my routers vpn client sends the dns requests encrypted over the vpn tunnel to the hosted vpn server? (currently tested ok for dns leaks - but that's hard to know if the dns requests are just redirected from the vpn server - and potentially still sent in plain text to the vpn server)

If the dns requests are encrypted, then rather than setting up a ras. pi locally (or similar) - I would rather have the dns server hosted with the vpn - as that is a better setup for me.

from dns.

Hi yunti.

Thanks for your interest! And thanks to wei for helping out!

From what I understand, you should have your vpn server use the dns container.

You can also use it on your client side so that your client's ISP can't see to what domain you tunnel to, but that's essentially for paranoids.

I'll update the diagrams to show it as a local area network.

from dns.