Ubuntu
network-manager package

  1. Bug #959037
  2. Comment #56

Comment 56 for bug 959037

Revision history for this message
Alkis Georgopoulos (alkisg) wrote : Re: NM-controlled dnsmasq prevents other DNS servers from running, yet network-manager doesn't Conflict with their packages

I tested bind-interfaces and except-interface=lo in the past (comment #26), it worked as advertised. I haven't yet tested them in the chained dnsmasq mode, but I guess it would work if I'm using a static IP (which isn't always the case for LTSP servers, some teachers use their laptops for LTSP servers). With a dynamic IP, I'd have to open the NM-connection editor all the time to update my primary DNS server. So a loopback address for the dnsmasq service would be preferred locally, while the non-loopback one would again be required for the LTSP clients.

> Network-manager simply drops a file with
> except-interface=lo

What I meant in comment #51 is that libvirt then won't be able to ship with
> except-interface=lxcbr0
 because it's a syntax error to specify 2 except-interface directives. Maybe it could be allowed in some future dnsmasq version, with the list of declared interfaces being merged.