summary refs log tree commit diff
path: root/docs
diff options
context:
space:
mode:
authorBrendan Abolivier <babolivier@matrix.org>2020-02-18 14:07:41 +0000
committerBrendan Abolivier <babolivier@matrix.org>2020-02-18 14:07:41 +0000
commitd009535639116ba27268a44ed2cd5514a9f8a6a8 (patch)
tree08f6afd833d47c44fb449ee4d64546e5f073d72d /docs
parentArgh trailing spaces (diff)
downloadsynapse-d009535639116ba27268a44ed2cd5514a9f8a6a8.tar.xz
Add mention of SRV records as an advanced topic
Diffstat (limited to 'docs')
-rw-r--r--docs/delegate.md10
1 files changed, 10 insertions, 0 deletions
diff --git a/docs/delegate.md b/docs/delegate.md
index 4126fffe71..7b55827cec 100644
--- a/docs/delegate.md
+++ b/docs/delegate.md
@@ -44,6 +44,16 @@ therefore cannot gain access to the necessary certificate. With .well-known,
 federation servers will check for a valid TLS certificate for the delegated
 hostname (in our example: `synapse.example.com`).
 
+## SRV DNS record delegation
+
+It is also possible to do delegation using a SRV DNS record. However, that is
+considered an advanced topic since it's a bit complex to set up, and `.well-known`
+delegation is already enough in most cases.
+
+However, if you really need it, you can find some documentation on how such a
+record should look like and how Synapse will use it in [the Matrix
+specification](https://matrix.org/docs/spec/server_server/latest#resolving-server-names).
+
 ## Delegation FAQ
 
 ### When do I need delegation?