<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Hi Vladimir,</p>
<p>Yes, NSD supports that. Because NSD is designed to copy the data
to the client, the signatures and the DNSKEY data can be sent
straight away.</p>
<p>The support itself consists of code to parse identifiers used
when reading the zone file. If that concluded successfully, then
the further operations should be unproblematic.</p>
<p>ldns-keygen and ldns-signzone have been updated in the code
repository with the new algorithms.<br>
</p>
<p>Best regards, Wouter<br>
</p>
<div class="moz-cite-prefix">On 26/03/2019 05:21, Vladimir Lomov
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:20190326042128.GD894@smoon.vl-lomov.ru">
<pre class="moz-quote-pre" wrap="">Hello,
the current ldns-keygen/ldns-signzone doesn't support ED25519/ED448
KSK/ZSK keys while dnssec-keygen can generate ED25519 keys. I generated
ED25519 KSK and ZSK keys using dnssec-keygen, published them in zone
file, checked the zone file (it is Ok) and sign zone by dnssec-signzone.
Though NSD was restarted successfully I wonder (actually I concern) does
NSD works fine with such keys?
I'm asking because I faced with strange problem with one of Registrar
(name.com) which supports ED25519/ED448 keys but their web interface
being able retrieve DNSKEY record from my DNS server unable to register
on their side the DS record for my DNS server.
Could it be that NSD couldn't work with ED25519 and sending wrong data
to Registrar when it tries to form DS record?
---
WBR, Vladimir Lomov
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
nsd-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:nsd-users@NLnetLabs.nl">nsd-users@NLnetLabs.nl</a>
<a class="moz-txt-link-freetext" href="https://open.nlnetlabs.nl/mailman/listinfo/nsd-users">https://open.nlnetlabs.nl/mailman/listinfo/nsd-users</a>
</pre>
</blockquote>
</body>
</html>