From 38472bf13570f2cf3c41ac430b50f3c4c2bb9c3f Mon Sep 17 00:00:00 2001 From: Steven Martin Date: Tue, 18 Jun 2024 15:28:07 -0400 Subject: [PATCH] [v14] docs: networking proxy update (#43207) * docs: networking proxy update * docs: update comment on public address --- docs/pages/reference/networking.mdx | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/docs/pages/reference/networking.mdx b/docs/pages/reference/networking.mdx index d0cd4a18a3902..a21e3b46f8eeb 100644 --- a/docs/pages/reference/networking.mdx +++ b/docs/pages/reference/networking.mdx @@ -14,9 +14,18 @@ configuration file. The public address can take an IP or a DNS name. It can also be a list of values: ```yaml -public_addr: ["proxy-one.example.com", "proxy-two.example.com"] +public_addr: ["service1.example.com", "service2.example.com"] ``` + + Only a single Proxy Service `public_addr` should be configured. Attempting + to have multiple addresses can result in redirects to the first listed address + that may not be available to the client. + + Specifying a public address for a Teleport service may be useful in the following use cases: