From: Marcin Siodelski <marcin@isc.org>
Date: Wed, 11 Mar 2015 12:14:24 +0000 (+0100)
Subject: [3688] Added description of the hostname reservations in the kea guide.
X-Git-Tag: trac3764_base~12^2~9
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3232c090d399047dc7c70e13efc325063bbde5e9;p=thirdparty%2Fkea.git

[3688] Added description of the hostname reservations in the kea guide.
---

diff --git a/doc/guide/dhcp4-srv.xml b/doc/guide/dhcp4-srv.xml
index a5c4362cbd..46224bc566 100644
--- a/doc/guide/dhcp4-srv.xml
+++ b/doc/guide/dhcp4-srv.xml
@@ -2124,10 +2124,22 @@ temporarily override a list of interface names and listen on all interfaces.
 
     <section id="reservation4-hostname">
       <title>Reserving a hostname</title>
-      <!-- @todo: replace this with the actual text once #3688 is implemented -->
-      <para>Reserving a hostname is currently not supported. It is possible
-      to specify that information in the configuration file, but that data
-      is not used by the server engine yet.</para>
+      <para>When the reservation for the client includes the <command>hostname
+      </command>, the server will assign this hostname to the client and send
+      it back in the Client FQDN or Hostname option, depending on which of them
+      the client has sent to the server. The reserved hostname always takes
+      precedence over the hostname supplied by the client or the autogenerated
+      (from the IPv4 address) hostname. If the reservation for the hostname is
+      specified the server ignores the <command>qualifying-suffix</command>
+      parameter and treats the value specified in the reservation as a fully
+      qualified name.</para>
+
+      <note>
+        <para>Future Kea versions may provide additional configuration
+        parameters to specify whether the reserved hostname is a fully qualified
+        name or the suffix should be appended.
+        </para>
+      </note>
     </section>
 
     <section id="reservation4-options">