> The configuration itself shipped by default should be patched
If you mean something like:
except-interface=lo
bind-interfaces
...I just tested them and they do allow both dnsmasq instances to run.
But of course those settings won't be acceptable to most dnsmasq users, as listening on "lo" is usually desired too (local DNS cache; DHCP/TFTP for VMs etc). So I don't think that crippling the default dnsmasq functionality is a good way to solve this problem. DNS clients shouldn't hook port 53; it's reserved for DNS servers.
> The configuration itself shipped by default should be patched
If you mean something like:
except-interface=lo
bind-interfaces
...I just tested them and they do allow both dnsmasq instances to run.
But of course those settings won't be acceptable to most dnsmasq users, as listening on "lo" is usually desired too (local DNS cache; DHCP/TFTP for VMs etc). So I don't think that crippling the default dnsmasq functionality is a good way to solve this problem. DNS clients shouldn't hook port 53; it's reserved for DNS servers.