From 5be09a1981ebea09b5c12e5900642979a75d7a6a Mon Sep 17 00:00:00 2001 From: Dan Heath <76443935+Dan-Heath@users.noreply.github.com> Date: Tue, 22 Apr 2025 19:08:53 +0000 Subject: [PATCH] backport of commit 1dda1c462c28e9c0143912bf8178e43f0903512b --- website/content/docs/api-clients/client-agent.mdx | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/website/content/docs/api-clients/client-agent.mdx b/website/content/docs/api-clients/client-agent.mdx index d5226bcb5e..9814ed4c00 100644 --- a/website/content/docs/api-clients/client-agent.mdx +++ b/website/content/docs/api-clients/client-agent.mdx @@ -17,7 +17,11 @@ When the Boundary Client Agent runs alongside an authenticated Boundary client, If you enter a hostname that matches a Boundary alias that the client is authorized to establish a session to, Boundary automatically generates the session and transparently proxies the connection on your behalf. If the Boundary Client Agent cannot find an alias, or if there are any issues with authentication, network connectivity, or latency, the Client Agent defers DNS resolution to the previously configured DNS resolvers. -Note that you must enable both IPv4 and IPv6 protocols for your environment to ensure the Client Agent can start and perform DNS lookups. + + +You must enable both IPv4 and IPv6 protocols for your environment to ensure the Client Agent can start and perform DNS lookups. + + ## Security