Comment 62 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

OK, so the ::1 idea fails as a quick hack. The alternatives seem to be as follows.

1. Either we accept that nm-dnsmasq is incompatible with every standalone nameserver and enforce this in a better way;
2. or we force every standalone nameserver into bind-interfaces mode and move nm-dnsmasq's listen address to something other than 127.0.0.1;
3. or we make nm-dnsmasq listen on another port number (using the --port option) and enhance glibc to support accessing nameservers at ports other than 53.

Have I forgotten any?

#3 is the most attractive option but requires the most work and won't happen soon. In the short term the choice is between #1 and #2.