-1838. [bug] fdupont
- The DHCPv6 sent multiple instances of an option or a
- sub-option when it seems to be requested more than once
- directly by the client or using the always-send flag.
- (Gitlab #1449)
+1838. [bug] tmark
+ kea-dhcp4 and kea-dhcp6 now calculate the DDNS TTL value
+ based on RFC 4702, Section 5 which suggests that the
+ TTL value be 1/3 of the lease's valid life time with a
+ minimum value of 10 minutes. Prior to this the servers
+ set the TTL to equal to the lease's valid life time.
+ (Gitlab #936)
1837. [doc] cstrotm
Several Kea ARM corrections.
reassigning either FQDNs or IP addresses. Doing so will cause kea-dhcp4
to generate DNS removal requests to D2.
+.. note::
+
+
+ The DNS entries Kea creates contain a value for TTL (time to live). As of
+ Kea 1.9.3, kea-dhcp4 calculates that value based on
+ `RFC 4702, Section 5 <https://tools.ietf.org/html/rfc4702#section-5>`__
+ which suggests that the TTL value be 1/3 of the lease's life time with
+ a minimum value of 10 minutes. Prior to this the server set the TTL value
+ equal to the lease's valid life time. Future releases may add one or
+ more parameters to customize this value.
+
.. _dhcpv4-d2-io-config:
DHCP-DDNS Server Connectivity
reassigning either FQDNs or IP addresses. Doing so causes kea-dhcp6
to generate DNS removal requests to D2.
+.. note::
+
+ The DNS entries Kea creates contain a value for TTL (time to live). As of
+ Kea 1.9.3, kea-dhcp6 calculates that value based on
+ `RFC 4702, Section 5 <https://tools.ietf.org/html/rfc4702#section-5>`__
+ which suggests that the TTL value be 1/3 of the lease's life time with
+ a minimum value of 10 minutes. Prior to this the server set the TTL value
+ equal to the lease's valid life time. Future releases may add one or
+ more parameters to customize this value.
.. _dhcpv6-d2-io-config: