Re: DNSSEC and DLZ

Mark Goldfinch <[email protected]> Fri, 1 Jan 2016 18:35:17 +1300
Newsgroups gmane.network.dns.bind9.dlz
Message-ID <CAK7eGc1pS+XWcVO92fKWnvTvb7jibABT_zrMYe6mxzJiiQsR2A@mail.gmail.com>
--===============2040946411385566108==
Content-Type: multipart/alternative; boundary=001a1130d226f4443605283f221a

--001a1130d226f4443605283f221a
Content-Type: text/plain; charset=UTF-8

On 1 Jan 2016 6:24 p.m., "Evan Hunt" <[email protected]> wrote:
> > - is there any reference documentation I can draw upon?
>
> Not that I know of, but there may be some Red Hat documentation I haven't
> seen.  How about I start up a conversation between you and me and the RH
> developers next week after the post-holiday work backlog settles down
> a bit?  (If you don't hear from me by Thursday, poke me.)

That sounds like a great idea.

The inability to run DNSSec via DLZ is a serious limitation. This plus the
other disadvantages like performance tradeoffs should be noted within
documentation.

--001a1130d226f4443605283f221a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr"><br>
On 1 Jan 2016 6:24 p.m., &quot;Evan Hunt&quot; &lt;<a href=3D"mailto:each@i=
sc.org">[email protected]</a>&gt; wrote:<br>
&gt; &gt; - is there any reference documentation I can draw upon?<br>
&gt;<br>
&gt; Not that I know of, but there may be some Red Hat documentation I have=
n&#39;t<br>
&gt; seen.=C2=A0 How about I start up a conversation between you and me and=
 the RH<br>
&gt; developers next week after the post-holiday work backlog settles down<=
br>
&gt; a bit?=C2=A0 (If you don&#39;t hear from me by Thursday, poke me.)</p>
<p dir=3D"ltr">That sounds like a great idea.</p>
<p dir=3D"ltr">The inability to run DNSSec via DLZ is a serious limitation.=
 This plus the other disadvantages like performance tradeoffs should be not=
ed within documentation.<br>
</p>

--001a1130d226f4443605283f221a--


--===============2040946411385566108==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------

--===============2040946411385566108==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Bind-dlz-testers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bind-dlz-testers

--===============2040946411385566108==--