I'd prefer to be able to set custom DNS to a BIND9 server on my LAN

### Is it a bug? - [x] I know this is an issue with the app, and contacting Mullvad support is not relevant. ### I have checked if others have reported this already - [x] I have checked the issue tracker to see if others have reported similar issues. ### Current Behavior Currently, I can't (see title) because the GUI refuses 192.168.101.10 as DNS resolver. I know something similar has been reported several times, but the GUI still refuses a LAN IP. I have a full bind server on a server on my LAN and it's been serving the whole LAN for decades. It's configured to forward to a mullvad DoH dnsproxy when mullvad is ON and to a quad DoH dnsproxy otherwise. It's been working flawlessly with nordvpn and mullvad VPNs using either openvpn or wireguard. All the PCs connected to my LAN use 192.168.101.10 for DNS and all wireguard config files use it as DNS. I've been using wireguard setup on all my machines since day one. Enough of history and presentation. Recently, on my Fedora 42 PC I want ahead and installed the mullvad vpn program. No problem so far, except I can't change the DNS. It's stuck to one of the 100.x.x.x. ### Expected Behavior I'd like to point mullvad vpn program's dns to my own server. For that to be true, the GUI should accept 192.168.101.10 in 192.168.101.0/24. ### Steps to Reproduce 1. ... With the GUI running, deselect all adguard vpns 2. ... Be certain the 'share LAN' is ticked 3. ... Add an IP within your LAN into personal DNS erver 4. ... The GUI will ignore the entry. ### Failure Logs ```shell ``` ### Operating system version Fedora 42 ### Mullvad VPN app version 2026.1, first install of the program ### Additional Information Actual setup on the Fedora PC where the mullvad vpn program is running. Firewall iss ufw. ``` xxxxxx@xxxxxx:~$ ip addr 2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 9c:rd ff:ff:ff:ff:ff:ff altname enx9cde0b inet 192.168.101.1/24 brd 192.168.101.255 scope global dynamic noprefixroute enp3s0 valid_lft 38141sec preferred_lft 38141sec inet6 2a9/64 scope global dynamic noprefixroute valid_lft 5049sec preferred_lft 2349sec inet6 fe80/64 scope link noprefixroute valid_lft forever preferred_lft forever 4: wg0-mullvad: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1420 qdisc fq_codel state UNKNOWN group default qlen 500 link/none inet 10.134.216.199/32 scope global wg0-mullvad valid_lft forever preferred_lft forever inet6 fc00/128 scope global valid_lft forever preferred_lft forever inet6 fe80/64 scope link stable-privacy proto kernel_ll valid_lft forever preferred_lft forever xxxxxx@xxxxxx:~$ sudo resolvectl status Global Protocols: LLMNR=resolve -mDNS DNSOverTLS=opportunistic DNSSEC=allow-downgrade/unsupported resolv.conf mode: stub Link 2 (enp3s0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 Protocols: +DefaultRoute LLMNR=resolve -mDNS DNSOverTLS=opportunistic DNSSEC=allow-downgrade/unsupported Current DNS Server: 192.168.101.10 DNS Servers: 192.168.101.10 Default Route: yes Link 4 (wg0-mullvad) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 Protocols: +DefaultRoute LLMNR=resolve -mDNS -DNSOverTLS DNSSEC=allow-downgrade/supported Current DNS Server: 100.64.0.23 DNS Servers: 100.64.0.23 DNS Domain: ~. Default Route: yes xxxxxx@xxxxxx:~$ dig -p 5353 @192.168.101.10 AAAA ns1.test-ipv6.com +short 2400:8907::2000:27ff:fecc:f29f xxxxxx@xxxxxx:~$ dig AAAA ns1.test-ipv6.com ns1.test-ipv6.com. 60 IN AAAA 2400:8907::2000:27ff:fecc:f29f ;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP) xxxxxx@xxxxxx:~$ cat /etc/resolv.conf nameserver 127.0.0.53 options edns0 trust-ad search . ```