Yes, /etc/NetworkManager/dnsmasq.d/lxd.conf would need to be generated and NetworkManager restarted when the user reconfigures the package. This happens rarely though - most users, just once when they do the initial setup.
I do not think that NetworkManager needs to restarted at any other times. When the bridge is down, the ip address in the dnsmasq.d config does not exist and .lxd lookups will simply fail as expected. When the bridge is brought back up, .lxd domain lookups would start working again. Just like when any other nameserver becomes unreachable for a period of time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1571967 Title: .lxd domain resolution not working after standard installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1571967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
