On 16/07/16 12:16, Albert ARIBAUD wrote:
> Alright... I'm out of ideas, sorry -- apart from recompiling dnsmasq
> with ad hoc debug code. :/
>
I can't see anything obvious from what's been posted so far, but it
might be worth pointing out that this arrangement is used in millions of
openWRT rout
On 15/07/16 00:13, mmmfotografie wrote:
> On 14-7-2016 23:22, Simon Kelley wrote:
>> On 12/07/16 00:17, mmmfotografie wrote:
>>> On 11-7-2016 23:08, Simon Kelley wrote:
I just tried all those domains using 2.76 and 8.8.8.8 upstream and all
behaved correctly. 194.109.9.99 won't talk to me,
Bonjour,
Le Sat, 16 Jul 2016 07:15:55 + (UTC)
Sébastien Delafond a écrit:
> On 2016-07-15, Albert ARIBAUD wrote:
> > No mention of the interfaces it binds to and how? No functional
> > equivalent to the interface-related options of dnsmasq?
>
> You can pass interfaces to bind to on the c
On 2016-07-15, Albert ARIBAUD wrote:
> No mention of the interfaces it binds to and how? No functional
> equivalent to the interface-related options of dnsmasq?
You can pass interfaces to bind to on the command-line, but it wasn't
necessary in my case.
> Which seems to imply that dnsmasq makes t
