Skip to content

Commit

Permalink
docs: Fixes examples for alias_refresh_interval & dns_request_timeout (
Browse files Browse the repository at this point in the history
…#5544) (#5548)

* docs: Fixes examples for alias_refresh_interval & dns_request_timeout

* Update website/content/docs/api-clients/client-agent.mdx



---------

Co-authored-by: Aditya Sharma <[email protected]>
Co-authored-by: Robin Beck <[email protected]>
Co-authored-by: Michael Li <[email protected]>
  • Loading branch information
4 people authored Feb 13, 2025
1 parent 2830fae commit 94026ab
Showing 1 changed file with 6 additions and 2 deletions.
8 changes: 6 additions & 2 deletions website/content/docs/api-clients/client-agent.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -99,14 +99,14 @@ The configuration file contains the following fields:

Example:
```hcl
alias_refresh_interval=60s
alias_refresh_interval="60s"
```

- `dns_request_timeout` - Specifies for how long the Client Agent DNS request handling, including any recursion, is allowed to run before it is canceled.

Example:
```hcl
dns_request_timeout=300s
dns_request_timeout="300s"
```

- `interface_to_use` - Specifies the interface to use instead of the default.
Expand Down Expand Up @@ -521,6 +521,10 @@ Follow the troubleshooting steps to understand why the Client Agent is not able
On MacOS versions 15.1 and 15.2, the firewall may incorrectly block the Client Agent from sending DNS responses. To resolve this issue,
upgrade to MacOS version 15.3 or later.

It may be neccessary to explicitly allow the `boundary-client-agent` process access to incoming network connections.

From the Firewall options in System Settings, toggle the `boundary-client-agent` to **Allow incoming connections**.

#### WARNING! Remote host indentification has changed! It is possible that someone is doing something nasty!

This error arises when you use an alias to connect to an SSH target after the first successful connection using that alias. The issue occurs because Boundary workers generate a new host key on every new SSH connection. You can safely ignore the warning using the `StrictHostKeyChecking=no` command line option:
Expand Down

0 comments on commit 94026ab

Please sign in to comment.