Sorry, I've been a bit swamped and this fell through the cracks, I'll try and find some time this week to try with the updated config.
In answer to your previous question: yes, the dig was the first thing I did following a reboot each time with the intention of providing the smallest number of log lines that would need to be examined but during which the problem had definitely occurred. I'll let you know the results of trying with the tweaked config ASAP. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns Status in network-manager package in Ubuntu: Incomplete Status in network-manager source package in Bionic: Incomplete Bug description: On 18.04.2 the `upgrade network-manager:amd64 1.10.6-2ubuntu1.1 1.10.14-0ubuntu2` lead to scoped DNS servers defined in `/etc/systemd/resolved.conf.d/*.conf` being ignored. Downgrading with `sudo apt-get install network- manager=1.10.6-2ubuntu1.1` has resolved the issue for now. Example systemd-resolved conf: [Resolve] Cache=no DNS=127.0.0.54 Domains=~.local.org.com Where 127.0.0.54:53 is bound to a dnsmasq server capable of resolving queries in that subdomain. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
