@@ -321,20 +321,19 @@ string in the standard format would be:
321
321
mongodb://mongodb1.example.com:27317,mongodb2.example.com:27017/?connectTimeoutMS=300000&replicaSet=mySet&authSource=aDifferentAuthDB
322
322
323
323
.. note::
324
- The ``mongodb+srv`` option will fail if there is no available DNS
324
+
325
+ The ``mongodb+srv`` option fails if there is no available DNS
325
326
with records that correspond to the hostname identified in the
326
- connection string. In addition, use of the ``+srv`` connection string modifier
327
- automatically sets the :urioption:`tls` (or the equivalent
328
- :urioption:`ssl`) option to ``true`` for the connection. You can
329
- override this behavior by explicitly setting the :urioption:`tls`
327
+ connection string. If you use the ``+srv`` connection string modifier,
328
+ the :urioption:`tls` (or the equivalent :urioption:`ssl`) option is
329
+ set to ``true`` for the connection. You can override this behavior by
330
+ explicitly setting the :urioption:`tls`
330
331
(or the equivalent :urioption:`ssl`) option to ``false`` with
331
332
``tls=false`` (or ``ssl=false``) in the query string.
332
333
333
- .. see::
334
-
335
- :ref:`example-connect-mongo-using-srv` provides an example of
336
- connecting :binary:`~bin.mongosh` to a replica set using
337
- the DNS Seed list Connection Format.
334
+ For an example that connects :binary:`~bin.mongosh` to a replica set using
335
+ the DNS seed list connection format, see :ref:`mongosh Connection Options
336
+ <example-connect-mongosh-using-srv>`.
338
337
339
338
340
339
.. _connections-connection-options:
0 commit comments