Infrastructure: DNS on systems with systemd-resolved

For Ubuntu

https://medium.com/@niktrix/getting-rid-of-systemd-resolved-consuming-port-53-605f0234f32f

sudo lsof -i -P -n | grep LISTEN
sudo systemctl stop systemd-resolved
vi /etc/systemd/resolved.conf

[Resolve]
DNS=8.8.8.8
DNSStubListener=no

sudo ln -sf /run/systemd/resolve/resolv.conf /etc/resolv.conf

https://www.tecmint.com/set-permanent-dns-nameservers-in-ubuntu-debian/

* apt install resolvconf
* nano /etc/resolvconf/resolv.conf.d/head
* nameserver 8.8.8.8
* nameserver 8.8.4.4

https://stackoverflow.com/questions/40877643/apt-get-install-in-ubuntu-16-04-docker-image-etc-resolv-conf-device-or-reso

* RUN apt-get update
* RUN apt-get install -y apt-utils debconf-utils dialog
* RUN echo 'debconf debconf/frontend select Noninteractive' | debconf-set-selections
* RUN echo "resolvconf resolvconf/linkify-resolvconf boolean false" | debconf-set-selections
* RUN apt-get update
* RUN apt-get install -y resolvconf

No repository file, test, or implementation entry point is identified. Start by reproducing the DNS failure on Ubuntu with systemd-resolved and review the project's Docker or infrastructure configuration; done means the affected setup resolves DNS without requiring an undocumented manual workaround.

Written by the indexing model from the issue text.