feature request: disabled DNSnet automatically when connected to selected wifi networks

[spyro1248]

Hi,

Whilst i love using DNSnet on my mobile connection, or on untrustworthy wifi, at home I trust my DNS.

It would be immensely useful if i could list 'safe' networks so that DNSnet would disable itself and allow me to resolve local hosts without it's interference.

For example, my EV charger is not accessible from the internet, nor does it have publicly visible DNS.

I'd quite like to not have to turn off DNSnet manually so i can charge my car.

[mnirun]

It's possible by using Tasker app.

More information can be found here #37.

It's possible by using Tasker app.

More information can be found here #37.

Tasker is not FOSS: #37 (comment) . So basically this is not a solution.

[tag6]

Making the decision if you're in your home network dependent on WLAN is not the right way. I see that in the Home Assistant App: Detecting the right WLAN is not sufficient and they struggle implementing all the complicated ways how to detect a simple thing. Now they implemented that you can activate "if some VPN is active you're at home". But users of DNSNet always have VPN active and still may use another VPN to access the home network, this is just the wrong approach.

You can access your local network using USB, Bluetooth, IR. You can activate a VPN (ok, unfortunately this conflicts with DNSNet anyway, as you can have only one VPN). There may exist a WLAN using the same name like your WLAN you'd like to use which is not your home network. You can rename your WLAN for some reason, then you have several devices where you need to change settings. You better do not define one or more interfaces/WLAN.

You want to detect your home network. You may want to define "if some address is available and some response is (blabla, maybe an SSL certificate check or domain, router available, DNS is your router, service available like your NAS or your home Assistant or PV or something like that) then I'm in my home network where other settings are to be used".

In the description of this issue the "selected wifi networks" do not appear, but the title shows this (imho bad) idea.

[spyro1248]

I agree - you are right.

I think if the option were available with a warning that "Fake networks may fool it", then it would probably be "good enough" for most "domestic" users.

An option to challenge a https server (and maybe check the certificate) would be a good way to implement this, as I could easily configure my Nextcloud server machine (which lives in my home) to reply to such a request only on my local network.

Another solution which would resolve the immediate issue in my original post would be to allow exemptions from DNSnet so that for specific domains it passes the request to the local DNS server.