On Fri, May 29, 2020 at 05:14:39PM +0000, Brian King wrote: > That is correct; in Rackspace cloud, DNS is set 'automatically' via > cloud-init and the config-drive's network-data.json on Ubuntu and the > RHEL family distros (RHEL, Fedora, CentOS) using their stock Openstack > images. > > >> I have to wonder if this bug report could be relevant: > > https://launchpad.net/bugs/1850310 > > Yes, this comment appears to be most relevant: > https://bugs.launchpad.net/cloud-init/+bug/1850310/comments/2 . Based > on my tests, adding the resolvconf package to the Debian 10 cloud > image and rerunning cloud-init does resolve the issue (no pun > intended!). In contrast, enabling systemd-resolve (which is already > present on the image) does NOT fix the issue. >
Have you tested against newer versions of cloud-init? Is the behavior the same there? Bullseye contains cloud-init 20.2, and you can find current images in https://cloud.debian.org/images/cloud/bullseye/daily/ noah
