summary refs log tree commit diff
path: root/develop/print.html
diff options
context:
space:
mode:
Diffstat (limited to 'develop/print.html')
-rw-r--r--develop/print.html8
1 files changed, 8 insertions, 0 deletions
diff --git a/develop/print.html b/develop/print.html
index 36cb826a3f..120ff4a671 100644
--- a/develop/print.html
+++ b/develop/print.html
@@ -1666,6 +1666,14 @@ generally not suitable if Synapse is hosted at a subdomain such as
 <p>It is also possible to do delegation using a SRV DNS record. However, that is generally
 not recommended, as it can be difficult to configure the TLS certificates correctly in
 this case, and it offers little advantage over <code>.well-known</code> delegation.</p>
+<p>Please keep in mind that server delegation is a function of server-server communication,
+and as such using SRV DNS records will not cover use cases involving client-server comms.
+This means setting global client settings (such as a Jitsi endpoint, or disabling
+creating new rooms as encrypted by default, etc) will still require that you serve a file
+from the <code>https://&lt;server_name&gt;/.well-known/</code> endpoints defined in the spec! If you are
+considering using SRV DNS delegation to avoid serving files from this endpoint, consider
+the impact that you will not be able to change those client-based default values globally,
+and will be relegated to the featureset of the configuration of each individual client.</p>
 <p>However, if you really need it, you can find some documentation on what such a
 record should look like and how Synapse will use it in <a href="https://matrix.org/docs/spec/server_server/latest#resolving-server-names">the Matrix
 specification</a>.</p>