Commit 0a597936 authored by Francis Dupont's avatar Francis Dupont
Browse files

[540-recommend-moving-hostname-char-set-and-hostname-char-replacement-out-of-d...

[540-recommend-moving-hostname-char-set-and-hostname-char-replacement-out-of-dhcp-ddns] Final improvements
parent d94754cb
......@@ -792,6 +792,16 @@
// T2 = valid lifetime * .75.
"t2-percent": .75,
// String of zero or more characters with which to replace each
// invalid character in the hostname or Client FQDN. The default
// value is an empty string which will cause invalid characters
// to be omitted rather than replaced.
"hostname-char-replacement": "x",
// Regular expression describing the invalid character set in
// the hostname or Client FQDN.
"hostname-char-set": "[^A-Za-z0-9.-]",
// List of loggers used by the servers using this configuration file.
"loggers": [
{
......
......@@ -751,6 +751,16 @@
// T2 = valid lifetime * .75.
"t2-percent": .75,
// String of zero or more characters with which to replace each
// invalid character in the hostname or Client FQDN. The default
// value is an empty string which will cause invalid characters
// to be omitted rather than replaced.
"hostname-char-replacement": "x",
// Regular expression describing the invalid character set in
// the hostname or Client FQDN.
"hostname-char-set": "[^A-Za-z0-9.-]",
// List of loggers used by the servers using this configuration file.
"loggers": [
{
......
......@@ -3219,6 +3219,13 @@ It is merely echoed by the server.
invalid characters.
</para>
</note>
<note>
Since the 1.6.0 Kea release it is possible to specify hostname-char-set
and/or hostname-char-replacement at the global scope. This allows
to sanitize host names without requiring a dhcp-ddns entry. When
a hostname-char parameter is defined at the global scope and
in a dhcp-ddns entry the second (local) value is used.
</note>
</section>
</section>
......
......@@ -3039,6 +3039,13 @@ should include options from the new option space:
invalid characters.
</para>
</note>
<note>
Since the 1.6.0 Kea release it is possible to specify hostname-char-set
and/or hostname-char-replacement at the global scope. This allows
to sanitize host names without requiring a dhcp-ddns entry. When
a hostname-char parameter is defined at the global scope and
in a dhcp-ddns entry the second (local) value is used.
</note>
</section>
</section>
......
This diff is collapsed.
This diff is collapsed.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment