|
|
@@ -322,7 +322,7 @@ JSON validator is available at <ulink url="http://jsonviewer.stack.hu/"/>.
|
|
|
database host name must also be specified (although it should be noted that this
|
|
|
configuration may have a severe impact on server performance):
|
|
|
<screen>
|
|
|
-"Dhcp6": { "lease-database": { <userinput>"host": <replaceable>remote-host-name</replaceable>"</userinput>, ... }, ... }
|
|
|
+"Dhcp6": { "lease-database": { <userinput>"host": <replaceable>remote-host-name</replaceable></userinput>, ... }, ... }
|
|
|
</screen>
|
|
|
The usual state of affairs will be to have the database on the same machine as
|
|
|
the DHCPv6 server. In this case, set the value to the empty string:
|
|
|
@@ -1029,10 +1029,10 @@ temporarily override a list of interface names and listen on all interfaces.
|
|
|
"type": "ipv6-address".
|
|
|
"record-types": "",
|
|
|
"array": false,
|
|
|
- "encapsulate ""
|
|
|
+ "encapsulate": ""</userinput>
|
|
|
},
|
|
|
{
|
|
|
- "name": "subopt2",
|
|
|
+ <userinput>"name": "subopt2",
|
|
|
"code": 2,
|
|
|
"space": "isc",
|
|
|
"type": "string",
|
|
|
@@ -1402,27 +1402,68 @@ should include options from the isc option space:
|
|
|
</orderedlist>
|
|
|
The parameters controlling the generation of NCRs for submission to D2
|
|
|
are contained in the "dhcp-ddns" section of kea-dhcp6
|
|
|
- configuration. The default values for this section appears as follows:
|
|
|
+ configuration. The mandatory parameters for the DHCP DDNS configuration
|
|
|
+ are <command>enable-updates</command> which is unconditionally
|
|
|
+ required, and <command>qualifying-suffix</command> which has no
|
|
|
+ default value and is required when <command>enable-updates</command>
|
|
|
+ is set to <command>true</command>.
|
|
|
+
|
|
|
+ The two (disabled and enabled) minimal DHCP DDNS configurations are:
|
|
|
+<screen>
|
|
|
+"Dhcp6": {
|
|
|
+ "dhcp-ddns": {
|
|
|
+ <userinput>"enable-updates": false</userinput>
|
|
|
+ },
|
|
|
+ ...
|
|
|
+}
|
|
|
+</screen>
|
|
|
+ and for example:
|
|
|
<screen>
|
|
|
"Dhcp6": {
|
|
|
"dhcp-ddns": {
|
|
|
<userinput>"enable-updates": true,
|
|
|
- "server-ip": "127.0.0.1",
|
|
|
- "server-port": 53001,
|
|
|
- "sender-ip": "",
|
|
|
- "sender-port": 0,
|
|
|
- "max-queue-size": 1024,
|
|
|
- "ncr-protocol": "UDP",
|
|
|
- "ncr-format": "JSON",
|
|
|
- "override-no-update": false,
|
|
|
- "override-client-update": false,
|
|
|
- "replace-client-name": false,
|
|
|
- "generated-prefix": "myhost",
|
|
|
- "qualifying-suffix": "example.com"</userinput>
|
|
|
+ "qualifying-suffix": "example."</userinput>
|
|
|
},
|
|
|
...
|
|
|
}
|
|
|
</screen>
|
|
|
+
|
|
|
+ The default values for the "dhcp-ddns" section are as follows:
|
|
|
+ <itemizedlist>
|
|
|
+ <listitem><simpara>
|
|
|
+ <command>"server-ip": "127.0.0.1"</command>
|
|
|
+ </simpara></listitem>
|
|
|
+ <listitem><simpara>
|
|
|
+ <command>"server-port": 53001</command>
|
|
|
+ </simpara></listitem>
|
|
|
+ <listitem><simpara>
|
|
|
+ <command>"sender-ip": ""</command>
|
|
|
+ </simpara></listitem>
|
|
|
+ <listitem><simpara>
|
|
|
+ <command>"sender-port": 0</command>
|
|
|
+ </simpara></listitem>
|
|
|
+ <listitem><simpara>
|
|
|
+ <command>"max-queue-size": 1024</command>
|
|
|
+ </simpara></listitem>
|
|
|
+ <listitem><simpara>
|
|
|
+ <command>"ncr-protocol": "UDP"</command>
|
|
|
+ </simpara></listitem>
|
|
|
+ <listitem><simpara>
|
|
|
+ <command>"ncr-format": "JSON"</command>
|
|
|
+ </simpara></listitem>
|
|
|
+ <listitem><simpara>
|
|
|
+ <command>"override-no-update": false</command>
|
|
|
+ </simpara></listitem>
|
|
|
+ <listitem><simpara>
|
|
|
+ <command>"override-client-update": false</command>
|
|
|
+ </simpara></listitem>
|
|
|
+ <listitem><simpara>
|
|
|
+ <command>"replace-client-name": false</command>
|
|
|
+ </simpara></listitem>
|
|
|
+ <listitem><simpara>
|
|
|
+ <command>"generated-prefix": "myhost"</command>
|
|
|
+ </simpara></listitem>
|
|
|
+ </itemizedlist>
|
|
|
</para>
|
|
|
|
|
|
|
|
|
@@ -1694,9 +1735,12 @@ should include options from the isc option space:
|
|
|
}
|
|
|
</screen>
|
|
|
<para>
|
|
|
- The suffix used when generating a FQDN or when qualifying a partial name
|
|
|
- is specified by the <command>qualifying-suffix</command> parameter. There
|
|
|
- is no default value. To set its value simply set it to the desired string:
|
|
|
+ The suffix used when generating a FQDN or when qualifying a
|
|
|
+ partial name is specified by
|
|
|
+ the <command>qualifying-suffix</command> parameter. This
|
|
|
+ parameter has no default value, thus it is mandatory when
|
|
|
+ DDNS updates are enabled.
|
|
|
+ To set its value simply set it to the desired string:
|
|
|
</para>
|
|
|
<screen>
|
|
|
"Dhcp6": {
|
|
|
@@ -1717,8 +1761,8 @@ should include options from the isc option space:
|
|
|
</para>
|
|
|
<para>
|
|
|
where candidate-name is the partial name supplied in the REQUEST.
|
|
|
- For example, if FQDN domain name value was "some-computer" and assuming
|
|
|
- the default value for qualifying-suffix, the generated FQDN would be:
|
|
|
+ For example, if FQDN domain name value was "some-computer" and
|
|
|
+ qualifying-suffix "example.com", the generated FQDN would be:
|
|
|
</para>
|
|
|
<para>
|
|
|
some-computer.example.com.
|
|
|
@@ -1732,10 +1776,9 @@ should include options from the isc option space:
|
|
|
</para>
|
|
|
<para>
|
|
|
where address-text is simply the lease IP address converted to a
|
|
|
- hyphenated string. For example, if lease address is 3001:1::70E and
|
|
|
- default values are used for
|
|
|
- <command>generated-prefix</command> and <command>qualifying-suffix</command>, the
|
|
|
- generated FQDN would be:
|
|
|
+ hyphenated string. For example, if lease address is 3001:1::70E,
|
|
|
+ the qualifying suffix "example.com", and the default value is used for
|
|
|
+ <command>generated-prefix</command>, the generated FQDN would be:
|
|
|
</para>
|
|
|
<para>
|
|
|
myhost-3001-1--70E.example.com.
|
Francis Dupont