I tried to find a reasonable solution and looks that there are different approaches.
I wanted to stay at most within the distribution layout while keeping all business requirements fulfilled. This is what I tested: ```code # Install required package and reconfigure service plans (i.e. disable systemd-resolved, enable dnsmasq sudo apt-get install dnsmasq sudo systemctl disable systemd-resolved sudo systemctl stop systemd-resolved sudo systemctl enable dnsmasq # These two lines should work on most environments, but .. :-) # Just add or change 'dns=dnsmasq' to your NetworkManager.conf to the section [main] #sudo cp /etc/NetworkManager/NetworkManager.conf /etc/NetworkManager/NetworkManager.conf.backup #sudo bash -c 'cat /etc/NetworkManager/NetworkManager.conf.backup |sed -e "s/^dns=.*//"| sed -e "s/\[main\]/\[main\]\ndns=dnsmasq/" >/etc/NetworkManager/NetworkManager.conf' # Restart NetworkManager to make the change above applied sudo systemctl restart NetworkManager # This removes the systemd resolv.conf link only if it has NetworkManager replacement :-) ls /var/run/NetworkManager/resolv.conf && sudo rm /etc/resolv.conf # And add NetworkManager's resolv.conf available for the system resolver sudo ln -s /var/run/NetworkManager/resolv.conf /etc/resolv.conf ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1800329 Title: Ubnutu 18.04 LTS KDE Neon does not resolve local (or single name) queries through DHCP assigned DNS (cached) server on local network Status in systemd package in Ubuntu: Confirmed Bug description: Ubnutu 18.04 KDE Neon does not resolve local (or single name) queries through DHCP assigned DNS (cached) server on local network. ** How to reproduce? ** 1. Let's have local network (e.g. 192.168.123.0/24) connected to the Internet through router called GATE 2. The GATE provides local DNS server cache (via Dnsmasq) and contains couple of local name translations (e.g. SuperCooolLocalServer pointing to 192.168.123.50). 3. Let's have fresh new Ubuntu 18.04 (KDE Neon) 4. Connect to the local network through WIFI (WPA2 encrypted, jsut enter password) ** What happens? ** Any desktop application trying to connect to SuperCooolLocalServer will fail when resolving the name to IP. When tested in terminal "host SuperCooolLocalServer" will return SERVFAIL. ** What is expected? ** The system should resolve the name SuperCooolLocalServer to 192.168.123.50 as it did until Ubuntu 16.04 LTS. ** Observation ** The system should do the resolution in the same logic as other home appliances running various operating systems (my iPhone, my wife's Galaxy, ours Ubuntu 16.04LTS, Windows 7, 8.1 10 and our other network components running various Linux based distributions.) I did quick test and the bug shows also on clean Ubuntu 18.04 (without the KDE Neon flavour). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1800329/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
