[#2892] add a phrase about empty reservations for known clients

diff --git a/doc/sphinx/arm/dhcp4-srv.rst b/doc/sphinx/arm/dhcp4-srv.rst
index 47e481268132bc391c5d25a341a979b7b31113b7..afdafb7536badd4e85bb3f7c3ee7f352a38e089b 100644 (file)
--- a/doc/sphinx/arm/dhcp4-srv.rst
+++ b/doc/sphinx/arm/dhcp4-srv.rst
@@ -5921,7 +5921,9 @@ mechanism.
 
 The following example demonstrates this concept. It indicates a single IPv4 subnet
 and all clients will get an address from it. However, only known clients (those that
-have reservations) will get their default router configured.
+have reservations) will get their default router configured. Empty reservations
+i.e. reservations that only have the identification criterion, can be
+specifically useful in this regard of making the clients known.
 
 ::
 

diff --git a/doc/sphinx/arm/dhcp6-srv.rst b/doc/sphinx/arm/dhcp6-srv.rst
index 5b12ed49ff800b8646a8778abc93983d2e445405..86a5dfc0bb9bd1cd7ea33bae6fc2e77f5e266433 100644 (file)
--- a/doc/sphinx/arm/dhcp6-srv.rst
+++ b/doc/sphinx/arm/dhcp6-srv.rst
@@ -5133,7 +5133,9 @@ mechanism.
 
 The following example demonstrates this concept. It indicates a single IPv6 subnet
 and all clients will get an address from it. However, only known clients (those that
-have reservations) will get their default DNS server configured.
+have reservations) will get their default DNS server configured. Empty reservations
+i.e. reservations that only have the identification criterion, can be
+specifically useful in this regard of making the clients known.
 
 ::