The network-manager package still ships /etc/dnsmasq.d/network-manager
with "bind-interfaces" in it
and that breaks the TFTP server of dnsmasq
and sometimes even the DNS server of dnsmasq.
"bind-dynamic" is a little better, but too unreliable to be used in production.
So this bug is still not resolved, after 150 messages it was just made a little worse.
One workaround is to undo the "solution" offered in this bug report:
1) In /etc/NetworkManager/NetworkManager.conf, comment out: # dns=dnsmasq
2) And in /etc/dnsmasq.d/network-manager, comment out: #bind-interfaces
A better solution would be for Mathieu to create a separate package for the nm-spawned dnsmasq, one that would conflict with the real dnsmasq server so that it would be automatically uninstalled when the sysadmin would install the real dnsmasq.
I can send a patch for that if it will be accepted.
The network-manager package still ships /etc/dnsmasq. d/network- manager
with "bind-interfaces" in it
and that breaks the TFTP server of dnsmasq
and sometimes even the DNS server of dnsmasq.
"bind-dynamic" is a little better, but too unreliable to be used in production.
So this bug is still not resolved, after 150 messages it was just made a little worse.
One workaround is to undo the "solution" offered in this bug report: ager/NetworkMan ager.conf, comment out: # dns=dnsmasq d/network- manager, comment out: #bind-interfaces
1) In /etc/NetworkMan
2) And in /etc/dnsmasq.
A better solution would be for Mathieu to create a separate package for the nm-spawned dnsmasq, one that would conflict with the real dnsmasq server so that it would be automatically uninstalled when the sysadmin would install the real dnsmasq.
I can send a patch for that if it will be accepted.