``false`` allows such reservations to be created both in the Kea configuration
file and in the host database backend, via :ischooklib:`libdhcp_host_cmds.so`.
-This setting is currently supported by the most popular host database
-backends, i.e. MySQL and PostgreSQL.
-Host Cache (see :ref:`hooks-host-cache`), or the RADIUS backend
-(see :ref:`hooks-radius`). An attempt to set ``ip-reservations-unique``
-to ``false`` when any of these three backends is in use yields a
-configuration error.
+Setting ``ip-reservations-unique`` to ``false`` when using memfile, MySQL or PostgreSQL is supported.
+This setting is NOT supported when using Host Cache (see :ref:`hooks-host-cache`), and the RADIUS backend
+(see :ref:`hooks-radius`). These reservation backends simply do not support multiple reservations for the
+same IP. If either of these hooks are loaded and ``ip-reservations-unique`` is set to ``false``, then a
+configuration error will be emitted and the server will fail to start.
.. note::
allows such reservations to be created both in the Kea configuration
file and in the host database backend, via :ischooklib:`libdhcp_host_cmds.so`.
-This setting is currently supported by the most popular host database
-backends, i.e. MySQL and PostgreSQL.
-Host Cache (see :ref:`hooks-host-cache`), or the RADIUS backend
-(see :ref:`hooks-radius`). An attempt to set ``ip-reservations-unique``
-to ``false`` when any of these three backends is in use yields a
-configuration error.
+Setting ``ip-reservations-unique`` to ``false`` when using memfile, MySQL or PostgreSQL is supported.
+This setting is NOT supported when using Host Cache (see :ref:`hooks-host-cache`), and the RADIUS backend
+(see :ref:`hooks-radius`). These reservation backends simply do not support multiple reservations for the
+same IP. If either of these hooks are loaded and ``ip-reservations-unique`` is set to ``false``, then a
+configuration error will be emitted and the server will fail to start.
.. note::