This is an issue with Ubuntu. You will need to setup resolv.conf so it works for your scenario.
Since you are customizing 18.04 on a 16.04 system, I have a hunch #3 ~might~ work for you, but also look through the bugs in #1 or #2 for hints, or check option #4 as well.
Michael,
This is an issue with Ubuntu. You will need to setup resolv.conf so it works for your scenario.
Since you are customizing 18.04 on a 16.04 system, I have a hunch #3 ~might~ work for you, but also look through the bugs in #1 or #2 for hints, or check option #4 as well.
#1 See...
https:/ /bugs.launchpad .net/cubic/ +bug/1725840
#2 Or...
https:/ /bugs.launchpad .net/cubic/ +bug/1723568
#3 Or try...
ln -sr /run/systemd/ resolve/ resolv. conf /run/systemd/ resolve/ stub-resolv. conf
#4 Or try...
mkdir /run/systemd/ resolve/ resolve/ resolv. conf resolve/ resolv. conf /run/systemd/ resolve/ stub-resolv. conf
echo "nameserver 127.0.1.1
search network" | tee /run/systemd/
ln -sr /run/systemd/