Re: Configure DHCP to update IPv6 DNS records
[email protected] Mon, 16 Feb 2026 12:45:14 +0100
| Newsgroups | gmane.network.dhcp.isc.dhcp-server |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format.
--===============1685466947709477774==
Content-Type: multipart/alternative;
boundary="------------EJkmAFBQkdxMZDkamCbLgH9b"
This is a multi-part message in MIME format.
--------------EJkmAFBQkdxMZDkamCbLgH9b
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Hello everyone,
The Samba team tried here
https://lists.isc.org/pipermail/kea-users/2022-October/003560.html
four !! years ago to obtain "on-commit" support from the KEA team and
failed.
No thank you!
The KEA team is clearly not interested in the interests of DHCP users,
otherwise they would have long since created a human- and
machine-readable file format for the KEA configuration using EBNF,
lex and yacc. Here in Germany, a computer science student could do
this within three months as part of their master's thesis in the field
of compiler construction.
I am now leaving this thread and will ask my question elsewhere.
Best regards
Frank
Am 15.02.2026 um 14:15 schrieb Darren Ankney:
> Hi Frank,
>
> Before you expend a lot of effort on ISC DHCP, I just wanted to point
> out that it is long EOL. The replacement is Kea
> (https://www.isc.org/kea/) which has it's own mailing list:
> https://lists.isc.org/mailman/listinfo/kea-users This ISC DHCP
> (dhcp-users) user list is no longer very active.
>
> Thank you,
> Darren Ankney
>
>
--------------EJkmAFBQkdxMZDkamCbLgH9b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<pre>Hello everyone,
The Samba team tried here
<a class="moz-txt-link-freetext" href="https://lists.isc.org/pipermail/kea-users/2022-October/003560.html">https://lists.isc.org/pipermail/kea-users/2022-October/003560.html</a>
four !! years ago to obtain "on-commit" support from the KEA team and
failed.
No thank you!</pre>
<pre>The KEA team is clearly not interested in the interests of DHCP users,
otherwise they would have long since created a human- and
machine-readable file format for the KEA configuration using EBNF,
lex and yacc. Here in Germany, a computer science student could do
this within three months as part of their master's thesis in the field
of compiler construction.
I am now leaving this thread and will ask my question elsewhere.
Best regards
Frank
</pre>
<br>
<div class="moz-cite-prefix">Am 15.02.2026 um 14:15 schrieb Darren
Ankney:<br>
</div>
<blockquote type="cite"
cite="mid:CAKabWHi1AFtobuMNDf1ukmUY4BxGjpMcWwZe+3ZAZxw-DUdj_Q@mail.gmail.com">
<pre wrap="" class="moz-quote-pre">Hi Frank,
Before you expend a lot of effort on ISC DHCP, I just wanted to point
out that it is long EOL. The replacement is Kea
(<a class="moz-txt-link-freetext" href="https://www.isc.org/kea/">https://www.isc.org/kea/</a>) which has it's own mailing list:
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/kea-users">https://lists.isc.org/mailman/listinfo/kea-users</a> This ISC DHCP
(dhcp-users) user list is no longer very active.
Thank you,
Darren Ankney
</pre>
<br>
</blockquote>
</body>
</html>
--------------EJkmAFBQkdxMZDkamCbLgH9b--
--===============1685466947709477774==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
--
ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information.
dhcp-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/dhcp-users
--===============1685466947709477774==--