Commit 1d9abefe authored by Marcin Siodelski's avatar Marcin Siodelski
Browse files

[3281] Corrected bind10-guide DHCP server limitation sections.

parent 0a5a96b3
...@@ -3848,7 +3848,7 @@ Dhcp4/dhcp-ddns/qualifying-suffix "example.com" string ...@@ -3848,7 +3848,7 @@ Dhcp4/dhcp-ddns/qualifying-suffix "example.com" string
</para> </para>
</section> </section>
<section> <section id="ipv4-subnet-id">
<title>IPv4 Subnet Identifier</title> <title>IPv4 Subnet Identifier</title>
<para> <para>
Subnet identifier is a unique number associated with a particular subnet. Subnet identifier is a unique number associated with a particular subnet.
...@@ -5047,19 +5047,11 @@ Dhcp4/dhcp-ddns/qualifying-suffix "example.com" string ...@@ -5047,19 +5047,11 @@ Dhcp4/dhcp-ddns/qualifying-suffix "example.com" string
yet</quote>, rather than actual limitations.</para> yet</quote>, rather than actual limitations.</para>
<itemizedlist> <itemizedlist>
<listitem> <!-- see tickets #3234, #3281 --> <listitem> <!-- see tickets #3234, #3281 -->
<para> <simpara>
On-line configuration has some limitations. Adding new subnets or Removal of a subnet during server reconfiguration may cause renumbering
modifying existing ones work, as is removing the last subnet from of auto-generated subnet identifiers, as described in section
the list. However, removing non-last (e.g. removing subnet 1,2 or 3 if <xref linkend="ipv4-subnet-id"/>.
there are 4 subnets configured) will cause issues. The problem is </simpara>
caused by simplistic subnet-id assignment. The subnets are always
numbered, starting from 1. That subnet-id is then used in leases
that are stored in the lease database. Removing non-last subnet will
cause the configuration information to mismatch data in the lease
database. It is possible to manually update subnet-id fields in
MySQL database, but it is awkward and error prone process. A better
reconfiguration support is planned.
</para>
</listitem> </listitem>
<listitem> <listitem>
<para> <para>
...@@ -5338,7 +5330,7 @@ Dhcp6/dhcp-ddns/qualifying-suffix "example.com" string ...@@ -5338,7 +5330,7 @@ Dhcp6/dhcp-ddns/qualifying-suffix "example.com" string
</para> </para>
</section> </section>
<section> <section id="ipv6-subnet-id">
<title>IPv6 Subnet Identifier</title> <title>IPv6 Subnet Identifier</title>
<para> <para>
Subnet identifier is a unique number associated with a particular subnet. Subnet identifier is a unique number associated with a particular subnet.
...@@ -6513,19 +6505,11 @@ Dhcp6/dhcp-ddns/qualifying-suffix "example.com" string ...@@ -6513,19 +6505,11 @@ Dhcp6/dhcp-ddns/qualifying-suffix "example.com" string
<itemizedlist> <itemizedlist>
<listitem> <!-- see tickets #3234, #3281 --> <listitem> <!-- see tickets #3234, #3281 -->
<para> <simpara>
On-line configuration has some limitations. Adding new subnets or Removal of a subnet during server reconfiguration may cause renumbering
modifying existing ones work, as is removing the last subnet from of auto-generated subnet identifiers, as described in section
the list. However, removing non-last (e.g. removing subnet 1,2 or 3 if <xref linkend="ipv6-subnet-id"/>.
there are 4 subnets configured) will cause issues. The problem is </simpara>
caused by simplistic subnet-id assignment. The subnets are always
numbered, starting from 1. That subnet-id is then used in leases
that are stored in the lease database. Removing non-last subnet will
cause the configuration information to mismatch data in the lease
database. It is possible to manually update subnet-id fields in
MySQL database, but it is awkward and error prone process. A better
reconfiguration support is planned.
</para>
</listitem> </listitem>
<listitem> <listitem>
......
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