diff --git a/doc/guide/dhcp4-srv.xml b/doc/guide/dhcp4-srv.xml
index 858d97b1bf..020902de84 100644
--- a/doc/guide/dhcp4-srv.xml
+++ b/doc/guide/dhcp4-srv.xml
@@ -496,7 +496,9 @@ the lease database after connectivity has been lost may be specified:
If the server is unable to reconnect to the database after making the maximum number
of attempts the server will exit. A value of zero (the default) disables automatic
recovery and the server will exit immediately upon detecting a loss of connectivity
-(MySQL and Postgres only).
+(MySQL and Postgres only). For Cassandra, Kea uses Cassandra interface that
+connects to all nodes in a cluster at the same time. Any connectivity
+issues should be handled by internal Cassandra mechanisms.
The number of milliseconds the server will wait between attempts to reconnect to the
diff --git a/doc/guide/dhcp6-srv.xml b/doc/guide/dhcp6-srv.xml
index c31a629f3f..f6a4f0ff2d 100644
--- a/doc/guide/dhcp6-srv.xml
+++ b/doc/guide/dhcp6-srv.xml
@@ -554,8 +554,7 @@ linkend="cassandra-database-configuration4"/> for details.
purpose, be it lease or hosts information. This arrangement gives the most
flexibility. Kea can keep leases and host reservations
separately, but can also point to the same database. Currently the
- supported hosts database types are MySQL and PostgreSQL; the Cassandra
- backend does not yet support host reservations.
+ supported hosts database types are MySQL, PostgreSQL and Cassandra.
For example, the following configuration can be used to
configure connection to MySQL:
@@ -627,7 +626,9 @@ the host database after connectivity has been lost may be specified:
If the server is unable to reconnect to the database after making the maximum number
of attempts the server will exit. A value of zero (the default) disables automatic
recovery and the server will exit immediately upon detecting a loss of connectivity
-(MySQL and Postgres only).
+(MySQL and Postgres only). For Cassandra, Kea uses Cassandra interface that
+connects to all nodes in a cluster at the same time. Any connectivity
+issues should be handled by internal Cassandra mechanisms.
The number of milliseconds the server will wait between attempts to reconnect to the