On 14/06/12 16:06, Thomas Hood wrote:
> @Alkis: IIUC dnsmasq in bind-interfaces mode will not start to listen on
> any addresses assigned to interfaces after dnsmasq has started. So,
> yes, she would have to restart standalone dnsmasq if she wants it to
> listen on those newly assigned addresses.
That's correct. The chief advantage of listening on the wildcard address
is that it all works as interfaces come and go. You lose that with
--bind-interfaces.
It would be possible these days to have dnsmasq detect extra interfaces
and bind to their addresses automatically, but the code to do that isn't
portable.
On 14/06/12 16:06, Thomas Hood wrote:
> @Alkis: IIUC dnsmasq in bind-interfaces mode will not start to listen on
> any addresses assigned to interfaces after dnsmasq has started. So,
> yes, she would have to restart standalone dnsmasq if she wants it to
> listen on those newly assigned addresses.
That's correct. The chief advantage of listening on the wildcard address
is that it all works as interfaces come and go. You lose that with
--bind-interfaces.
It would be possible these days to have dnsmasq detect extra interfaces
and bind to their addresses automatically, but the code to do that isn't
portable.
Simon.