mirror of
https://git.anonymousland.org/anonymousland/synapse.git
synced 2024-09-06 14:41:58 +00:00
Incorporate review
This commit is contained in:
parent
61b457e3ec
commit
71d65407e7
@ -1,13 +1,14 @@
|
|||||||
# Delegation
|
# Delegation
|
||||||
|
|
||||||
Without configuring delegation, homeservers will expect the server
|
By default, other homeservers will expect to be able to reach yours via
|
||||||
responsible for resources using e.g. `example.com` as their `server_name`
|
your `server_name`, on port 8448. For example, if you set your `server_name`
|
||||||
(e.g. `@user:example.com`) to be served at `example.com:8448`.
|
to `example.com` (so that your user names look like `@user:example.com`),
|
||||||
|
other servers will try to connect to yours at `https://example.com:8448/`.
|
||||||
|
|
||||||
Delegation is a Matrix feature allowing a homeserver admin to retain a
|
Delegation is a Matrix feature allowing a homeserver admin to retain a
|
||||||
`server_name` of `example.com` so that your user IDs, room aliases, etc
|
`server_name` of `example.com` so that user IDs, room aliases, etc continue
|
||||||
continue to look like `*:example.com`, whilst having your federation
|
to look like `*:example.com`, whilst having federation traffic routed
|
||||||
traffic routed to a different server and/or port (e.g. `synapse.example.com:443`).
|
to a different server and/or port (e.g. `synapse.example.com:443`).
|
||||||
|
|
||||||
## .well-known delegation
|
## .well-known delegation
|
||||||
|
|
||||||
@ -37,8 +38,8 @@ should return:
|
|||||||
Note, specifying a port is optional. If no port is specified, then it defaults
|
Note, specifying a port is optional. If no port is specified, then it defaults
|
||||||
to 8448.
|
to 8448.
|
||||||
|
|
||||||
With .well-known, federation servers will check for a valid TLS certificate
|
With .well-known delegation, federating servers will check for a valid TLS
|
||||||
for the delegated hostname (in our example: `synapse.example.com`).
|
certificate for the delegated hostname (in our example: `synapse.example.com`).
|
||||||
|
|
||||||
## SRV DNS record delegation
|
## SRV DNS record delegation
|
||||||
|
|
||||||
|
@ -12,10 +12,10 @@ it is also the domain that other servers will use to try to reach your
|
|||||||
server (via port 8448). This is easy to set up and will work provided
|
server (via port 8448). This is easy to set up and will work provided
|
||||||
you set the `server_name` to match your machine's public DNS hostname.
|
you set the `server_name` to match your machine's public DNS hostname.
|
||||||
|
|
||||||
You will also need a valid TLS certificate for this `server_name` served
|
For this default configuration to work, you will need to listen for TLS
|
||||||
on port 8448. The preferred way to do that is by using a reverse proxy,
|
connections on port 8448. The preferred way to do that is by using a
|
||||||
see [reverse_proxy.md](<reverse_proxy.md>) for instructions on how to
|
reverse proxy: see [reverse_proxy.md](<reverse_proxy.md>) for instructions
|
||||||
correctly set one up.
|
on how to correctly set one up.
|
||||||
|
|
||||||
In some cases you might not want to run Synapse on the machine that has
|
In some cases you might not want to run Synapse on the machine that has
|
||||||
the `server_name` as its public DNS hostname, or you might want federation
|
the `server_name` as its public DNS hostname, or you might want federation
|
||||||
|
Loading…
Reference in New Issue
Block a user