Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Allow per-network DNS settings #178

Open
thislooksfun opened this issue Feb 7, 2025 · 0 comments
Open

[Feature Request] Allow per-network DNS settings #178

thislooksfun opened this issue Feb 7, 2025 · 0 comments

Comments

@thislooksfun
Copy link

thislooksfun commented Feb 7, 2025

I have a few local devices on my network that I connect to via local domain names managed by a pi-hole instance. I'd like to keep using that setup while still getting the benefits of having a VPN for the rest of my traffic. The issue is that if I configure the iOS app to use a custom DNS server pointing at my pi-hole then everything works just fine... right up until I leave the house, at which point it can no longer connect to my pi-hole. And even worse, if I then connect to another network my phone will try to connect to the device there, which could end up being insecure.

I could get around this with adding a second DNS server (i.e. Quad9), but I'm under the impression that DNS requests will round-robin through the listed servers, not use them as a failover. Plus it still has the other-network IP collision issue mentioned above.

My ideal solution is two parts:

  1. Expand the Automation system to allow configuring DNS settings on a per-network-connection basis.
  2. (optional, but would make it more seamless) add more options to the DNS settings to mirror the desktop apps; notably "Use Existing DNS".

This way I could use my local DNS server at home, and PIA DNS / Quad9 / some other private DNS server on all other networks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant