Matthias Andree wrote:
> Am 16.02.2011 17:41, schrieb Simon Kelley:
>
>>> in that case, dnsmasq binds to 192.168.0.4 according to lsof.
>>>
>>>
>>> Is this a known issue on FreeBSD? What means are there to resolve this
>>> so that users don't fall into this trap?
>>>
>> The behavior is the same
Am 16.02.2011 17:41, schrieb Simon Kelley:
>> in that case, dnsmasq binds to 192.168.0.4 according to lsof.
>>
>>
>> Is this a known issue on FreeBSD? What means are there to resolve this
>> so that users don't fall into this trap?
>>
>
> The behavior is the same on all platforms.
>
> Without
Matthias Andree wrote:
> Situation:
>
> dnsmasq 2.56 supposed to answer all but loopback. named (system default
> BIND 9.6.3, FreeBSD 8.2-PRERELEASE amd64) is bound to 127.0.0.1 and ::1
> port 53, confirmed with lsof. dnsmasq config is as follows:
>
> domain-needed
> bogus-priv
> no-resolv
>
Situation:
dnsmasq 2.56 supposed to answer all but loopback. named (system default
BIND 9.6.3, FreeBSD 8.2-PRERELEASE amd64) is bound to 127.0.0.1 and ::1
port 53, confirmed with lsof. dnsmasq config is as follows:
domain-needed
bogus-priv
no-resolv
no-poll
server=127.0.0.1
except-interface
