It seems to me that each of maas, cloud-init and netplan could do better here.
a.) maas declares 'global' nameserver/dns info. this is kind of silly in that such a thing doesn't really exist. maas has the information necessary to declare the nameserver on the device with the address that has a route to it. b.) cloud-init is currently sticking that global definition on an interface that doesnt have an address. so cloud-init could do better. c.) netplan or systemd-networkd could realize enp0s25 interface is "up" and that it should have its nameservers used. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750884 Title: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
