trafficserver-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [trafficserver] branch master updated: Explain how SRV origin selection works
Date Tue, 20 Aug 2019 20:33:03 GMT
This is an automated email from the ASF dual-hosted git repository.

mlibbey pushed a commit to branch master
in repository

The following commit(s) were added to refs/heads/master by this push:
     new 101c79b  Explain how SRV origin selection works
101c79b is described below

commit 101c79b10a7ce81c250d7489fcdaa12aef7169db
Author: Miles Libbey <>
AuthorDate: Mon Aug 19 14:36:11 2019 -0700

    Explain how SRV origin selection works
 doc/admin-guide/files/records.config.en.rst | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/doc/admin-guide/files/records.config.en.rst b/doc/admin-guide/files/records.config.en.rst
index 0de9158..05bdbd2 100644
--- a/doc/admin-guide/files/records.config.en.rst
+++ b/doc/admin-guide/files/records.config.en.rst
@@ -2453,7 +2453,14 @@ DNS
-   Indicates whether to use SRV records for origin server lookup.
+   Enables (``1``) or disables (``0``) the use of SRV records for origin server
+   lookup. |TS| will use weights found in the SRV record as a weighted round
+   robin in origin selection. Note that |TS| will lookup
+   ``_$scheme._$internet_protocol.$origin_name``. For instance, if the origin is
+   set to ````, |TS| would lookup ````.
+   Also note that the port returned in the SRV record MUST match the port being
+   used for the origin (e.g. if the origin scheme is http and a default port, there
+   should be a SRV record with port 80).
 .. ts:cv:: CONFIG proxy.config.dns.dedicated_thread INT 0

View raw message