This is an automated email from the ASF dual-hosted git repository.
mlibbey pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/trafficserver.git
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 <[email protected]>
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
:reloadable:
:overridable:
- 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 ``https://my.example.com``, |TS| would lookup
``_https._tcp.my.example.com``.
+ 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
