>From the IRC discussion: 23:01 < RAOF> stgraber: I don't suppose there's a way to get the best of both worlds? Have dnsmasq ignore the interfaces you need, *and* pick up new interfaces? 23:01 < RAOF> For example: how disruptive is restarting dnsmasq?
Please note that Simon Kelley is working on enhancing dnsmasq so that it will automatically detect new interfaces and addresses (on LInux, anyway). That's much better than restarting dnsmasq. Once that enhancement is available, forcing dnsmasq into bind-interfaces mode will be less disruptive. Forcing dnsmasq into bind-interfaces mode now is disruptive, but not terribly so; stgraber argues (persuasively, IMHO) that libvirt and lxc should force standalone dnsmasq into bind-interfaces mode even without the aforemention enhancement. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/231060 Title: packages dnsmasq and libvirt-bin conflict with each other To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/231060/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
