Ubuntu
network-manager package

  1. Bug #959037
  2. Comment #48

Comment 48 for bug 959037

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

Aha, I had tried this and it didn't work... in version 2.57. But I see that quantal already has 2.62.

> Another instance of dnsmasq will run without interfering with that, providing only that --bind-interfaces is set.

Just to make sure I understand correctly: Do you mean here that --bind-interfaces has to be set on both instances of dnsmasq? Or will one instance (the NM-controlled one) with --bind-interfaces coexist nicely with another (the standalone dnsmasq) which doesn't use that option and listens on 0.0.0.0?

NM already runs dnsmasq with --bind-interfaces and --listen-address (specifically, --listen-address=127.0.0.1) so we would only be changing the address.

Mathieu mentioned earlier the possibility of using 127.0.1.1 which happens to be the address assigned (in /etc/hosts) to the system hostname on some (but not all) systems. Is there any advantage to using 127.0.1.1 as opposed to another 127.* address?