Sorry for the late answer but I was on holiday. I tested the patch from git
and it works as expected. Thank you a lot.
On Sun, Aug 9, 2015 at 6:46 PM, Simon Kelley
wrote:
> On 06/06/15 09:59, Ermanno Scaglione wrote:
> > auth-server=owncloud.local.lan,wan
> >
Hi Kevin,
There's RFC 6303 for that, current status is best current practice.
As for dnsmasq implementation of that recommendations, it could depend on auth
support, since it enables zone support.
Best Regards, Vladislav Grishenko
> -Original Message-
> From: Dnsmasq-discuss
Hi All,
After enabling dnsmasq's dns logging the other day I was a little
surprised to see queries for fe80:: being forwarded to my ISP's
resolvers. I'd say that they're extremely unlikely to know anything
about my link local stuff so as a solution I've added the following to
my config:
Ahh, excellent! Very helpful Vladislav. Looks like a have a few more
zones to not leak to the Internet :-)
Thanks,
Kevin
On 07/09/2015 15:54, Vladislav Grishenko wrote:
> Hi Kevin,
>
> There's RFC 6303 for that, current status is best current practice.
> As for dnsmasq implementation of that
On Sep 7, 2015, at 2:04 PM, Matt Taggart wrote:
> Hi,
>
> Have you seen this draft for adding TLS to DNS?
>
> https://tools.ietf.org/html/draft-ietf-dprive-start-tls-for-dns-01
>
> What would it take to implement in dnsmasq?
> Both as a server and as a client.
Take a
> but I cannot find any option for DLV.
ISC will stop accepting domains for DLV in 2016 and will terminate
service alltogether in 2017 [1]
-JP
[1] https://dlv.isc.org
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
Hi,
Have you seen this draft for adding TLS to DNS?
https://tools.ietf.org/html/draft-ietf-dprive-start-tls-for-dns-01
What would it take to implement in dnsmasq?
Both as a server and as a client.
I am thinking the client support would initially be more interesting,
as upstream DNS servers