Tracked in Github Issues as https://github.com/canonical/cloud- init/issues/3486
** Bug watch added: github.com/canonical/cloud-init/issues #3486 https://github.com/canonical/cloud-init/issues/3486 ** Changed in: cloud-init Status: Triaged => Expired -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1850310 Title: Debian 10/9/8 DNS configuration bug Status in cloud-init: Expired Bug description: I use cloud-init with NoCloud data source for configuring my VM's and got strange bug with DNS configuration on official Debian images like https://cdimage.debian.org/cdimage/openstack/current-10/debian-10-openstack- amd64.qcow2. My network config: ``` version: 2 ethernets: eth0: set-name: eth0 match: macaddress: <MAC address> addresses: [ <IP address> ] gateway4: <GATEWAY ADDRESS> nameservers: addresses: [8.8.8.8,8.8.4.4] ``` After creating new VM I got next configuration in /etc/network/interfaces.d/50-cloud-init.cfg which is seems ok: ``` auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 10.52.240.11/16 dns-nameservers 8.8.8.8 8.8.4.4 gateway 10.52.1.1 ``` But /etc/resolv.conf contains: ``` nameserver 127.0.0.1 ``` Which leads to the fact that I can’t resolve any domain name, for example: ``` # ping google.com ping: google.com: Temporary failure in name resolution ``` To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1850310/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
