Device: Jolla Phone (2026), SFOS 5.2.0.17
The new network stack on this device (wpa_supplicant + udhcpc + systemd-resolved, with connman no longer managing wifi) has a DNS configuration gap. Three things I hit today:
-
No DNS fields in WLAN settings. The per-connection page only offers proxy settings under Advanced. Nothing for DNS servers or search domains.
-
The panel shows DNS the phone isn’t actually using. My router advertises 192.168.1.254 via DHCP. I set the per-link DNS in systemd-resolved to 192.168.1.177 with .254 as fallback, and systemd-resolve --status confirms the phone resolves through .177 first. The WLAN settings panel still displays 192.168.1.254. It reads the DHCP lease, not the live resolver config, and there’s no way to tell that from the UI.
-
No CLI fallback shipped. This image doesn’t include connmanctl, resolvectl or systemd-networkd, so the terminal route is gone too. Setting DNS requires root and a manual systemd-resolve --interface=wlan0 --set-dns=… call, plus something to re-apply it after every DHCP renew or reconnect.
Why it matters: local DNS servers (Pi-hole, AdGuard Home), privacy resolvers (NextDNS, Quad9) and adblocking DNS are all unusable without hacks, and the UI actively misleads about what the phone is resolving through.
What I’d like to see:
- DNS server fields (primary/fallback) and search domains in the per-connection WLAN settings, written to the systemd-resolved per-link config
- resolvectl (and/or connmanctl) shipped in the image so the setting is manageable without developer mode
- The WLAN panel reading the effective per-link DNS instead of the raw DHCP lease