Comment 91 for bug 959037

Revision history for this message
Simon Kelley (simon-thekelleys) wrote : Re: [Bug 959037] Re: NM-controlled dnsmasq prevents other DNS servers from starting

On 18/06/12 21:08, Thomas Hood wrote:
> @Simon: This is pretty much what I had in mind (comment #88) as a long-
> term solution. How difficult do you think that this would be?

Don't know. I'm working on it now: seems to be behaving:

dnsmasq: new IPv4: 192.168.3.1
dnsmasq: new IPv6: fe80::f0f6:48ff:fe15:70b0

>
> (Moving nm-dnsmasq listening to another port than 53 is at best a veeery
> long-term solution since it requires first getting glibc enhanced, then
> getting all other resolver libraries enhanced, then waiting for third-
> party static binaries to be replaced by new versions built against
> enhanced libraries. That's a ten-year project.)
>
> If "bind-interfaces-dynamically" works well then I see no reason why it
> shouldn't be the default mode of operation. Indeed, I see no reason why
> it shouldn't be the *only* mode on OSs with support for it.
I see reasons: I've been burned by releasing changes that "won;t affect
anything" too many times, I like the idea of making the new behaviour
opt-in.

Simon.

>