Commit 14ce7e33 authored by Stephen Morris's avatar Stephen Morris
Browse files

[3468] Minor editorial changes during review

Including: ensuring consistent formaat for lists, ensuring
order of items in a list explaining an example JSON map
corresponds to the order of the elements in the map, etc.
parent 5f262cb1
...@@ -20,7 +20,7 @@ ...@@ -20,7 +20,7 @@
catalog of servers from which to select. In fact, D2 has two such catalogs, catalog of servers from which to select. In fact, D2 has two such catalogs,
one for forward DNS and one for reverse DNS; these catalogs are referred one for forward DNS and one for reverse DNS; these catalogs are referred
to as DDNS Domain Lists. Each list consists of one or more named DDNS to as DDNS Domain Lists. Each list consists of one or more named DDNS
Domains. Further, each DDNS Domain has a list of of one or more DNS Domains. Further, each DDNS Domain has a list of one or more DNS
servers that publish the DNS data for that domain. servers that publish the DNS data for that domain.
</para> </para>
<para> <para>
...@@ -50,18 +50,17 @@ ...@@ -50,18 +50,17 @@
</para> </para>
<section id="dhcp-ddns-server-start-stop"> <section id="dhcp-ddns-server-start-stop">
<title>Starting and Stopping the DHCP-DDNS Server</title> <title>Starting and Stopping the DHCP-DDNS Server</title>
<para>
It is recommended to control DHCPv4 server in Kea using <command>keactl</command>,
which is described in details in <xref linkend="keactrl"/>.
</para>
<para> <para>
<command>kea-dhcp-ddns</command> is the Kea DHCP-DDNS server and, <command>kea-dhcp-ddns</command> is the Kea DHCP-DDNS server
like other parts of Kea, is a separate binary that can be run on and, due to the nature of DDNS, it is run alongside either the
its own or through <command>keactl</command>. Due to the nature DHCPv4 or DHCPv6 components (or both). Like other parts of
of DDNS, it is run along with either DHCPv4 or DHCPv6 components Kea, is a separate binary that can be run on its own or through
(or both). <command>keactl</command> (see <xref linkend="keactrl"/>). In
normal operation, controlling <command>kea-dhcp-ddns</command>
with <command>keactl</command> is recommended.
</para> </para>
<para> <para>
Upon start up the module will load its configuration and begin listening Upon start up the module will load its configuration and begin listening
for NCRs based on that configuration. for NCRs based on that configuration.
...@@ -70,9 +69,9 @@ ...@@ -70,9 +69,9 @@
<section id="d2-configuration"> <section id="d2-configuration">
<title>Configuring the DHCP-DDNS Server</title> <title>Configuring the DHCP-DDNS Server</title>
<para> <para>
Before staring <command>kea-dhcp-ddns</command> module for the Before starting <command>kea-dhcp-ddns</command> module for the
first time, a configuration file needs to be created. The following default first time, a configuration file needs to be created. The following default
configuration seems reasonable in most cases: configuration is a template that can be customised to your requirements.
<screen> <screen>
<userinput>"DhcpDdns": { <userinput>"DhcpDdns": {
"ip_address": "127.0.0.1", "ip_address": "127.0.0.1",
...@@ -97,57 +96,63 @@ ...@@ -97,57 +96,63 @@
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<simpara> <simpara>
<command>Global Server Parameters</command> &mdash; <command>Global Server Parameters</command> -
values which control connectivity and global server behavior values which control connectivity and global server behavior
</simpara> </simpara>
</listitem> </listitem>
<listitem> <listitem>
<simpara> <simpara>
<command>TSIG Key Info</command> &mdash; <command>TSIG Key Info</command> -
defines the TSIG keys used for secure traffic with DNS servers defines the TSIG keys used for secure traffic with DNS servers
</simpara> </simpara>
</listitem> </listitem>
<listitem> <listitem>
<simpara> <simpara>
<command>Forward DDNS</command> &mdash; <command>Forward DDNS</command> -
defines the catalog of Forward DDNS Domains defines the catalog of Forward DDNS Domains
</simpara> </simpara>
</listitem> </listitem>
<listitem> <listitem>
<simpara> <simpara>
<command>Reverse DDNS</command> &mdash; <command>Reverse DDNS</command> -
defines the catalog of Forward DDNS Domains defines the catalog of Forward DDNS Domains
</simpara> </simpara>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
<section id="d2-server-parameter-config"> <section id="d2-server-parameter-config">
<title>Global Server Parameters</title> <title>Global Server Parameters</title>
<orderedlist> <itemizedlist>
<listitem><para>
ip_address - IP address on which D2 listens for requests. The default is <listitem><simpara>
the local loopback interface at address 127.0.0.1. You may specify <command>ip_address</command> - IP address on which D2
either an IPv4 or IPv6 address. listens for requests. The default is the local loopback interface at
</para></listitem> address 127.0.0.1. You may specify either an IPv4 or IPv6 address.
<listitem><para> </simpara></listitem>
port - Port on which D2 listens for requests. The default value
<listitem><simpara>
<command>port</command> - Port on which D2 listens for requests. The default value
is 53001. is 53001.
</para></listitem> </simpara></listitem>
<listitem><para>
ncr_format - Socket protocol to use when sending requests to D2. <listitem><simpara>
Currently only UDP is supported. TCP may be available in an upcoming <command>dns_server_timeout</command> - The maximum amount
release. of time in milliseconds, that D2 will wait for a response from a
</para></listitem> DNS server to a single DNS update message.
<listitem><para> </simpara></listitem>
ncr_protocol - Packet format to use when sending requests to D2.
<listitem><simpara>
<command>ncr_protocol</command> - Packet format to use when sending requests to D2.
Currently only JSON format is supported. Other formats may be available Currently only JSON format is supported. Other formats may be available
in future releases. in future releases.
</para></listitem> </simpara></listitem>
<listitem><para>
dns_server_timeout - The maximum amount of time in milliseconds, that <listitem><simpara>
D2 will wait for a response from a DNS server to a single DNS update <command>ncr_format</command> - Socket protocol to use when sending requests to D2.
message. Currently only UDP is supported. TCP may be available in an upcoming
</para></listitem> release.
</orderedlist> </simpara></listitem>
</itemizedlist>
<para> <para>
D2 must listen for change requests on a known address and port. By D2 must listen for change requests on a known address and port. By
default it listens at 127.0.0.1 on port 53001. The following example default it listens at 127.0.0.1 on port 53001. The following example
...@@ -207,7 +212,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section. ...@@ -207,7 +212,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section.
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<simpara> <simpara>
<command>name</command> &mdash; <command>name</command> -
a unique text label used to identify this key within the a unique text label used to identify this key within the
list. This value is used to specify which key (if any) should be list. This value is used to specify which key (if any) should be
used when updating a specific domain. So long as it is unique its used when updating a specific domain. So long as it is unique its
...@@ -218,7 +223,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section. ...@@ -218,7 +223,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section.
</listitem> </listitem>
<listitem> <listitem>
<simpara> <simpara>
<command>algorithm</command> &mdash; <command>algorithm</command> -
specifies which hashing algorithm should be used with this specifies which hashing algorithm should be used with this
key. This value must specify the same algorithm used for the key. This value must specify the same algorithm used for the
key on the DNS server(s). The supported algorithms are listed below: key on the DNS server(s). The supported algorithms are listed below:
...@@ -247,7 +252,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section. ...@@ -247,7 +252,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section.
</listitem> </listitem>
<listitem> <listitem>
<simpara> <simpara>
<command>secret</command> &mdash; <command>secret</command> -
is used to specify the shared secret key code for this key. This value is is used to specify the shared secret key code for this key. This value is
case sensitive and must exactly match the value specified on the DNS server(s). case sensitive and must exactly match the value specified on the DNS server(s).
It is a base64-encoded text value. It is a base64-encoded text value.
...@@ -303,12 +308,12 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section. ...@@ -303,12 +308,12 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section.
behavior. Currently it contains a single parameter, the catalog of behavior. Currently it contains a single parameter, the catalog of
forward DDNS Domains, which is a list of structures. forward DDNS Domains, which is a list of structures.
<screen> <screen>
<userinput>"DhcpDdns": { "DhcpDdns": {
"forward_ddns": { <userinput>"forward_ddns": {
"ddns_domains": [ ] "ddns_domains": [ ]
}, }</userinput>,
... ...
}</userinput> }
</screen> </screen>
By default, this list is empty, which will cause the server to ignore By default, this list is empty, which will cause the server to ignore
...@@ -317,13 +322,14 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section. ...@@ -317,13 +322,14 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section.
<section id="add-forward-ddns-domain"> <section id="add-forward-ddns-domain">
<title>Adding Forward DDNS Domains</title> <title>Adding Forward DDNS Domains</title>
<para> <para>
A forward DDNS Domain maps a forward DNS zone to a set of DNS servers A forward DDNS Domain maps a forward DNS zone to a set of
which maintain the forward DNS data for that zone. You will need one DNS servers which maintain the forward DNS data (i.e. name to
forward DDNS Domain for each zone you wish to service. It may very address mapping) for that zone. You will need one forward DDNS
well be that some or all of your zones are maintained by the same Domain for each zone you wish to service. It may very well
servers. You will still need one DDNS Domain per zone. Remember that be that some or all of your zones are maintained by the same
matching a request to the appropriate server(s) is done by zone and servers. You will still need one DDNS Domain per zone. Remember
a DDNS Domain only defines a single zone. that matching a request to the appropriate server(s) is done
by zone and a DDNS Domain only defines a single zone.
</para> </para>
<para> <para>
The section describes how to add Forward DDNS Domains. Repeat these The section describes how to add Forward DDNS Domains. Repeat these
...@@ -332,7 +338,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section. ...@@ -332,7 +338,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section.
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<simpara> <simpara>
<command>name</command> &mdash; <command>name</command> -
The fully qualified domain name (or zone) that this DDNS Domain The fully qualified domain name (or zone) that this DDNS Domain
can update. This is value used to compare against the request can update. This is value used to compare against the request
FQDN during forward matching. It must be unique within the FQDN during forward matching. It must be unique within the
...@@ -341,17 +347,16 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section. ...@@ -341,17 +347,16 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section.
</listitem> </listitem>
<listitem> <listitem>
<simpara> <simpara>
<command>key_name</command> &mdash; <command>key_name</command> -
If TSIG is used with this domain's servers, this If TSIG is used with this domain's servers, this
value should be the name of the key from within the TSIG Key List value should be the name of the key from within the TSIG Key List
to use. If the value is blank (the default), TSIG will not be to use. If the value is blank (the default), TSIG will not be
used in DDNS conversations with this domain's servers. Currently used in DDNS conversations with this domain's servers.
TSIG has not been implemented, so this value is ignored.
</simpara> </simpara>
</listitem> </listitem>
<listitem> <listitem>
<simpara> <simpara>
<command>dns_servers</command> &mdash; <command>dns_servers</command> -
A list of one or more DNS servers which can conduct the server A list of one or more DNS servers which can conduct the server
side of the DDNS protocol for this domain. The servers side of the DDNS protocol for this domain. The servers
are used in a first to last preference. In other words, when D2 are used in a first to last preference. In other words, when D2
...@@ -398,21 +403,21 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section. ...@@ -398,21 +403,21 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section.
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<simpara> <simpara>
<command>hostname</command> &mdash; <command>hostname</command> -
The resolvable host name of the DNS server. This value is not The resolvable host name of the DNS server. This value is not
yet implemented. yet implemented.
</simpara> </simpara>
</listitem> </listitem>
<listitem> <listitem>
<simpara> <simpara>
<command>ip_address</command> &mdash; <command>ip_address</command> -
The IP address at which the server listens for DDNS requests. The IP address at which the server listens for DDNS requests.
This may be either an IPv4 or an IPv6 address. This may be either an IPv4 or an IPv6 address.
</simpara> </simpara>
</listitem> </listitem>
<listitem> <listitem>
<simpara> <simpara>
<command>port</command> &mdash; <command>port</command> -
The port on which the server listens for DDNS requests. It The port on which the server listens for DDNS requests. It
defaults to the standard DNS service port of 53. defaults to the standard DNS service port of 53.
</simpara> </simpara>
...@@ -441,10 +446,13 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section. ...@@ -441,10 +446,13 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section.
} }
} }
</screen> </screen>
</para>
<note><simpara>
As stated earlier, "hostname" is not yet supported so, the parameter As stated earlier, "hostname" is not yet supported so, the parameter
"ip_address" must be set to the address of the DNS server. "ip_address" must be set to the address of the DNS server.
</para> </simpara></note>
</section> <!-- "add-forward-dns-servers" --> </section> <!-- "add-forward-dns-servers" -->
</section> <!-- "add-forward-ddns-domains" --> </section> <!-- "add-forward-ddns-domains" -->
...@@ -460,9 +468,10 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section. ...@@ -460,9 +468,10 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section.
reverse DDNS Domains, which is a list of structures. reverse DDNS Domains, which is a list of structures.
<screen> <screen>
"DhcpDdns": { "DhcpDdns": {
"reverse_ddns": { <userinput>"reverse_ddns": {
"ddns_domains": [ ] "ddns_domains": [ ]
} }</userinput>
...
} }
</screen> </screen>
By default, this list is empty, which will cause the server to ignore By default, this list is empty, which will cause the server to ignore
...@@ -471,14 +480,15 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section. ...@@ -471,14 +480,15 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section.
<section id="add-reverse-ddns-domain"> <section id="add-reverse-ddns-domain">
<title>Adding Reverse DDNS Domains</title> <title>Adding Reverse DDNS Domains</title>
<para> <para>
A reverse DDNS Domain maps a reverse DNS zone to a set of DNS servers A reverse DDNS Domain maps a reverse DNS zone to a set of DNS
which maintain the reverse DNS data for that zone. You will need one servers which maintain the reverse DNS data (address to name
reverse DDNS Domain for each zone you wish to service. It may very mapping) for that zone. You will need one reverse DDNS Domain
well be that some or all of your zones are maintained by the same for each zone you wish to service. It may very well be that
servers; even then, you will still need one DDNS Domain entry for each some or all of your zones are maintained by the same servers;
zone. Remember that even then, you will still need one DDNS Domain entry for each
matching a request to the appropriate server(s) is done by zone and zone. Remember that matching a request to the appropriate
a DDNS Domain only defines a single zone. server(s) is done by zone and a DDNS Domain only defines a
single zone.
</para> </para>
<para> <para>
The section describes how to add Reverse DDNS Domains. Repeat these The section describes how to add Reverse DDNS Domains. Repeat these
...@@ -487,7 +497,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section. ...@@ -487,7 +497,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section.
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<simpara> <simpara>
<command>name</command> &mdash; <command>name</command> -
The fully qualified reverse zone that this DDNS Domain The fully qualified reverse zone that this DDNS Domain
can update. This is the value used during reverse matching can update. This is the value used during reverse matching
which will compare it with a reversed version of the request's which will compare it with a reversed version of the request's
...@@ -501,7 +511,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section. ...@@ -501,7 +511,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section.
</listitem> </listitem>
<listitem> <listitem>
<simpara> <simpara>
<command>key_name</command> &mdash; <command>key_name</command> -
If TSIG should be used with this domain's servers, then this If TSIG should be used with this domain's servers, then this
value should be the name of that key from the TSIG Key List. value should be the name of that key from the TSIG Key List.
If the value is blank (the default), TSIG will not be If the value is blank (the default), TSIG will not be
...@@ -511,7 +521,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section. ...@@ -511,7 +521,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section.
</listitem> </listitem>
<listitem> <listitem>
<simpara> <simpara>
<command>dns_servers</command> &mdash; <command>dns_servers</command> -
a list of one or more DNS servers which can conduct the server a list of one or more DNS servers which can conduct the server
side of the DDNS protocol for this domain. Currently the servers side of the DDNS protocol for this domain. Currently the servers
are used in a first to last preference. In other words, when D2 are used in a first to last preference. In other words, when D2
...@@ -559,20 +569,20 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section. ...@@ -559,20 +569,20 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section.
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<simpara> <simpara>
<command>hostname</command> &mdash; <command>hostname</command> -
The resolvable host name of the DNS server. This value is The resolvable host name of the DNS server. This value is
currently ignored. currently ignored.
</simpara> </simpara>
</listitem> </listitem>
<listitem> <listitem>
<simpara> <simpara>
<command>ip_address</command> &mdash; <command>ip_address</command> -
The IP address at which the server listens for DDNS requests. The IP address at which the server listens for DDNS requests.
</simpara> </simpara>
</listitem> </listitem>
<listitem> <listitem>
<simpara> <simpara>
<command>port</command> &mdash; <command>port</command> -
The port on which the server listens for DDNS requests. It The port on which the server listens for DDNS requests. It
defaults to the standard DNS service port of 53. defaults to the standard DNS service port of 53.
</simpara> </simpara>
...@@ -601,10 +611,15 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section. ...@@ -601,10 +611,15 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section.
} }
} }
</screen> </screen>
</para>
<note>
<simpara>
As stated earlier, "hostname" is not yet supported so, the parameter As stated earlier, "hostname" is not yet supported so, the parameter
"ip_address" must be set to the address of the DNS server. "ip_address" must be set to the address of the DNS server.
</para> </simpara>
</note>
</section> <!-- "add-reverse-dns-servers" --> </section> <!-- "add-reverse-dns-servers" -->
</section> <!-- "add-reverse-ddns-domains" --> </section> <!-- "add-reverse-ddns-domains" -->
...@@ -698,8 +713,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section. ...@@ -698,8 +713,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section.
be rejected. be rejected.
</para> </para>
<para> <para>
The following series of commands in bindctl will create the Forward The following example configuration specified the Forward DDNS Domains.
DDNS Domains.
<screen><userinput> <screen><userinput>
"DhcpDdns": { "DhcpDdns": {
"forward_ddns": { "forward_ddns": {
...@@ -772,8 +786,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section. ...@@ -772,8 +786,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section.
the third domain. the third domain.
</para> </para>
<para> <para>
The following series of commands in bindctl will create our Reverse These Reverse DDNS Domains are specified as follows:
DDNS Domains.
<screen><userinput> <screen><userinput>
"DhcpDdns": { "DhcpDdns": {
......
...@@ -13,46 +13,49 @@ ...@@ -13,46 +13,49 @@
<!-- @todo Rewrite this section once #3422 is done --> <!-- @todo Rewrite this section once #3422 is done -->
<para> <para>
It is recommended to control DHCPv4 server in Kea using <command>keactl</command>, It is recommended that the Kea DHCPv4 server be started and stopped
which is described in details in <xref linkend="keactrl"/>. using <command>keactl</command> (described in <xref linkend="keactrl"/>).
</para> However, it is also possible to run the server directly: it accepts
the following command-line switches:
<para>
However, it is also possible to run the server on its own, not using any
scripts. The server accepts the following command-line parameters:
</para> </para>
<itemizedlist> <itemizedlist>
<listitem> <listitem>
<simpara>-c file - specifies the configuration file. This is the <simpara>
only mandatory parameter (it may be optional for configuration <command>-c <replaceable>file</replaceable></command> -
parameters other than Kea)</simpara> specifies the configuration file. This is the only mandatory
switch.</simpara>
</listitem> </listitem>
<listitem> <listitem>
<simpara>-v - specifies whether the server logging should be <simpara>
switched to verbose mode. In verbose mode, logging severity and <command>-v</command> - specifies whether the server
debuglevel specified in a configuration file are ignored and logging should be switched to verbose mode. In verbose mode,
severity debug and maximum debuglevel (99) is assumed. That flag is the logging severity and debuglevel specified in a configuration
convenient, for temporarily switching the server into maximum file are ignored and "debug" severity and the maximum debuglevel
verbosity, e.g. when debugging.</simpara> (99) are assumed. The flag is convenient, for temporarily
switching the server into maximum verbosity, e.g. when
debugging.</simpara>
</listitem> </listitem>
<listitem> <listitem>
<simpara>-p port - specifies UDP port the server will listen <simpara>
on. This is only useful during testing, as the DHCPv4 server <command>-p <replaceable>port</replaceable></command> -
listening on ports other than default DHCPv4 ports will not be able specifies UDP port the server will listen on. This is only
to handle regular DHCPv4 queries.</simpara> useful during testing, as the DHCPv4 server listening on
ports other than default DHCPv4 ports will not be able to
handle regular DHCPv4 queries.</simpara>
</listitem> </listitem>
</itemizedlist> </itemizedlist>
<para> <para>
The server running in a console can be shut down by pressing ctrl-c. The When running in a console, the server can be shut down by
server will detect such a key combination and will initialize shutdown procedure. pressing ctrl-c. It detects the key combination and shuts
down gracefully.
</para> </para>
<para> <para>
On start-up, the server will detect available network interfaces On start-up, the server will detect available network interfaces
and will attempt to open UDP sockets on all interfaces that and will attempt to open UDP sockets on all interfaces
are mentioned in the configuration file. mentioned in the configuration file.
</para> </para>
<para> <para>
...@@ -68,8 +71,8 @@ ...@@ -68,8 +71,8 @@
<title>Introduction</title> <title>Introduction</title>
<para> <para>
This section explains how to configure the DHCPv4 server using the This section explains how to configure the DHCPv4 server using the
Kea configuration backend. Kea configuration using any other Kea configuration backend. (Kea configuration using any other
backends is outside of scope for this document. Before DHCPv4 backends is outside of scope of this document.) Before DHCPv4
is started, its configuration file has to be created. The is started, its configuration file has to be created. The
basic configuration looks as follows: basic configuration looks as follows:
<screen> <screen>
...@@ -86,7 +89,7 @@ ...@@ -86,7 +89,7 @@
# Next we specify the type of lease database # Next we specify the type of lease database
"lease-database": { "lease-database": {
"type": "memfile", "type": "memfile",
"persist": true, "persist": "true",
"name": "/var/kea/dhcp4.leases" "name": "/var/kea/dhcp4.leases"
}, },
...@@ -119,7 +122,7 @@ one or more objects. In this specific example, we have only one ...@@ -119,7 +122,7 @@ one or more objects. In this specific example, we have only one
object called Dhcp4. This is a simplified configuration, as usually object called Dhcp4. This is a simplified configuration, as usually
there will be additional objects, like <command>Logging</command> or there will be additional objects, like <command>Logging</command> or
<command>DhcpDns</command>, but we omit them now for clarity. The Dhcp4 <command>DhcpDns</command>, but we omit them now for clarity. The Dhcp4
configuration starts with the the