[Dnsmasq-discuss] Loading Dnsmasq before the interface is up
Tsachi
tsachi.kimel at gmail.com
Wed Aug 15 16:34:47 BST 2012
Thanks Simon,
I use the "bind-interfaces" since I am going to run two instances of
dnsmasq, and without, the second fails to bind (address already in
use).
The second dnsmasq is configured to listen on a specific interface
after the interface is loaded.
I also tried to add "except-interface=XXXX" for the first instance,
but it didn’t do the trick for me.
Anyhow, the "bind-dynamic" option sounds great,
Will it give the user the ability to configure the IP address before
the IP assigned or it is intended for interface name only ?
Will the binding will take place when netlink receives an update?
Cheers,
Tsachi
> On Wed, Aug 15, 2012 at 6:23 AM, Simon Kelley <simon at thekelleys.org.uk> wrote:
>> On 15/08/12 14:15, Tsachi wrote:
>>> Just to correct, the dnsmasq was listening on 0.0.0.0:67 before the
>>> interface was up, so it is not the netlink message that cause it to
>>> listen and it was listening before.
>>> But still after the interface is up I don’t see the binding of the DNS.
>>>
>>> And my config file is:
>>>
>>> domain-needed
>>> bogus-priv
>>> bind-interfaces
>>> dhcp-range=10.0.0.10,10.0.0.10,10080m
>>> resolv-file=/etc/resolv.conf
>>> dhcp-authoritative
>>>
>>
>> Remove bind-interfaces from your configuration: that will cause dnsmasq
>> to listen on 0.0.0.0:53 also.
>>
>> The behaviour you're looking for (bind addresses as interfaces come up)
>> is not available. It will be available in dnsmasq 2.63 using a new
>> option, bind-dynamic instead of bind-interfaces. Dnsmasq 2.63 is due any
>> day now.
>>
>>
>> Cheers,
>>
>> Simon.
>>
More information about the Dnsmasq-discuss
mailing list