Hi again,
I reworked the original patch to contain fallback for older version of
nettle. It will work fine on more recent version (should be a bit faster
than original code), but still will compile for older libraries.
On 02/26/2018 09:12 PM, Petr Menšík wrote:
> Hi again,
>
> We at Fedora use
There's something very similar to this already in place for DHCPv6,
where it's allowed to specify
--dhcp-range=::,static
To allow any defined static allocation. For consistency, it may make
sense to simply use 0.0.0.0
so --dhcp-range=0.0.0.0,static
represents the special case. Netmask handling
On 11/03/18 02:43, Markus Hartung wrote:
> I have dug a little more and I can't think of this behaviour to be
> nothing else than a bug.
>
> I have made a simple config now to reproduce the bug:
>
> Start server with this command:
>
> dnsmasq -p 1153
Yes, they should be cached. The dnsmasq --log-queries option will tell
you when or not a particular answer comes from the cache, which should
give you confidence about what's happening in this case.
Cheers,
Simon.
On 12/03/18 17:53, Michael Tolan wrote:
> Hi all,
>
> I want to ask whether
Convergent evolution got me to
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=f3223fbff65d8ae9d67426dce6218fda30dee0cf
which achieves the same thing in a slightly different way. Are you happy
with that?
Cheers,
Simon.
On 15/03/18 16:40, Petr Menšík wrote:
> Hi again,
>
> I
On Thu, Mar 15, 2018 at 05:05:24PM +, Simon Kelley wrote:
>
> Anyone else have thoughts?
>
I think this sort of thing introduces new behavior that is not supported
by any DNS standard. Almost all of these resolv.conf-based dances
revolve around a handful of use cases:
1) Someone wants to
I'm worried that it takes so many words to describe what this does.
Configuration options are no good unless people can see what problem
they solve and understand when to use them.
I confess I'm not sure I understand when anyone would use this, and why.
It's not security, because it doesn't
On 2018-03-15 17:14, Simon Kelley wrote:
Is it a bug if it fulfils the specification? :-)
The section of the man page on AUTHORITATIVE CONFIGURATION lists all the
sources of data for an auth zone, and it doesn't include synth-domain.
So there's no bug :)
The main reason that synth-domain is not
