Skip to content

Commit 5516bcf

Browse files
committed
docs: remove dns discover
1 parent 30f6567 commit 5516bcf

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

docs/api/getting-started.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -38,8 +38,8 @@ To connect your application to KurrentDB, you need to configure and create a cli
3838
::: tip Insecure clusters
3939
The recommended way to connect to KurrentDB is using secure mode (which is
4040
the default). However, if your KurrentDB instance is running in insecure
41-
mode, you must explicitly set `tls=false` in your [connection
42-
string](#connection-string) or client configuration.
41+
mode, you must explicitly set `tls=false` in your connection
42+
string or client configuration.
4343
:::
4444

4545
KurrentDB uses connection strings to configure the client connection. The connection string supports two protocols:
@@ -93,7 +93,6 @@ There are a number of query parameters that can be used in the connection string
9393
| `keepAliveTimeout` | Number | `10` | Keep-alive ping call timeout, in seconds. |
9494
| `userCertFile` | String, file path | None | User certificate file for X.509 authentication. |
9595
| `userKeyFile` | String, file path | None | Key file for the user certificate used for X.509 authentication. |
96-
| `dnsDiscover` | `true`, `false` | `false` | Enable DNS-based cluster discovery. When `true`, resolves hostnames to discover cluster nodes. Use with `feature=dns-lookup` for full DNS resolution. |
9796
| `feature` | `dns-lookup` | None | Enable specific client features. Use `dns-lookup` with `dnsDiscover=true` to resolve hostnames to multiple IP addresses for cluster discovery. |
9897

9998
When connecting to an insecure instance, specify `tls=false` parameter. For example, for a node running locally use `kurrentdb://localhost:2113?tls=false`. Note that usernames and passwords aren't provided there because insecure deployments don't support authentication and authorisation.
@@ -218,4 +217,4 @@ latch.await();
218217
When you read events from the stream, you get a collection of `ResolvedEvent`
219218
structures (synchronous) or `ReadMessage` objects (reactive). The event payload
220219
is returned as a byte array and needs to be deserialized. See more advanced
221-
scenarios in [reading events documentation](./reading-events.md).
220+
scenarios in [reading events documentation](./reading-events.md).

0 commit comments

Comments
 (0)