If we don't know, then maybe things should be passed to netplan, in a way for it to generate global resolved config? as in, create /run/systemd/resolved.conf.d/global.conf
[Resolve] DNS=999.999.999.999 (Maybe FallbackDNS=, if we want it to leave DNS= setting for users to tweak) Or whatnot, which should then appear in systemd-resolve --status, Global section which is applied as a fallback if an interface does not have a per-interface DNS settings. Could somebody try dropping dns configs out of netplan file that is generated, rerun apply, check that systemd-resolve --status has nothing, then add above drop-in with the right dns server, restart resolved, and check if that picks up a global DNS server, and if network resolution works correctly? *globally* I also wonder, if .network / .link files should have an ability to specify Global DNS settings for resolved... -- 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
