2024-11-16 15:34:25 +00:00
# Configuring your DNS settings
2018-08-08 07:07:02 +00:00
2024-11-26 10:51:51 +00:00
< sup > [Prerequisites](prerequisites.md) > Configuring your DNS settings > [Getting the playbook ](getting-the-playbook.md ) > [Configuring the playbook ](configuring-playbook.md ) > [Installing ](installing.md )</ sup >
2024-11-05 12:38:26 +00:00
2018-08-08 07:07:02 +00:00
To set up Matrix on your domain, you'd need to do some DNS configuration.
2024-11-16 07:19:17 +00:00
## DNS setting for server delegation (optional)
2024-10-18 17:32:11 +00:00
2024-12-09 05:18:00 +00:00
In the sample `vars.yml` ([`examples/vars.yml`](../examples/vars.yml)), we recommend to use a short user ID like `@alice:example.com` instead of `@alice:matrix.example.com` .
2018-08-08 07:07:02 +00:00
2024-12-08 17:55:02 +00:00
To use such an ID, you don't need to install anything on the actual `example.com` server. Instead, you need to instruct the Matrix network that Matrix services for `example.com` are redirected over to `matrix.example.com` . This redirection is also known as "delegation".
2019-02-06 07:36:03 +00:00
2024-11-16 07:19:17 +00:00
As we discuss in [Server Delegation ](howto-server-delegation.md ), server delegation can be configured in either of these ways:
2019-02-06 07:36:03 +00:00
2024-11-16 07:19:17 +00:00
- Setting up a `/.well-known/matrix/server` file on the base domain (`example.com`)
- Setting up a `_matrix._tcp` DNS SRV record
For simplicity reasons, this playbook recommends you to set up server delegation via a `/.well-known/matrix/server` file, instead of using a DNS SRV record.
If you choose the recommended method (file-based delegation), you do not need to configure the DNS record to enable server delegation. You will need to add a necessary configuration later, when you [finalize the installation ](installing.md#finalize-the-installation ) after installing and starting Matrix services.
On the other hand, if you choose this method (setting up a DNS SRV record), you need to configure the additional DNS record as well as adjust SSL certificate handling. Take a look at this documentation for more information: [Server Delegation via a DNS SRV record (advanced) ](howto-server-delegation.md#server-delegation-via-a-dns-srv-record-advanced )
2019-02-06 07:36:03 +00:00
2021-03-24 04:05:48 +00:00
## DNS settings for services enabled by default
2019-02-05 09:07:08 +00:00
2024-11-17 08:10:40 +00:00
To serve the base domain (`example.com`) and [Element Web ](configuring-playbook-client-element-web.md ) with the default subdomain, adjust DNS records as below.
| Type | Host | Priority | Weight | Port | Target |
| ----- | ---------------------------- | -------- | ------ | ---- | ---------------------|
| A | `matrix` | - | - | - | `matrix-server-IP` |
2024-10-17 13:19:28 +00:00
| CNAME | `element` | - | - | - | `matrix.example.com` |
2020-03-23 15:13:58 +00:00
2024-11-17 08:10:40 +00:00
As the table illustrates, you need to create 2 subdomains (`matrix.example.com` and `element.example.com` ) and point both of them to your server's IP address (DNS `A` record or `CNAME` record is fine).
The `element.example.com` subdomain is necessary, because this playbook installs the [Element Web ](https://github.com/element-hq/element-web ) client for you by default. If you'd rather instruct the playbook not to install Element Web (`matrix_client_element_enabled: false` when [Configuring the playbook ](configuring-playbook.md ) later), feel free to skip the `element.example.com` DNS record.
2021-01-30 07:05:52 +00:00
Be mindful as to how long it will take for the DNS records to propagate.
Add "Quick start" guide (#3801)
* Add docs/quick-start.md
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Add description about keeping the playbook and services up-to-date
Also: move descriptions about difference between the playbook tags (setup-all and install-all) and about the just "recipe" from installing.md to maintenance-upgrading-services.md
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Replace <your-username> with YOUR_USERNAME_HERE
This is a common expression and should avoid misunderstanding that `<` and `>` would need to be included
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Replace <your-password> with YOUR_PASSWORD_HERE
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Change the link to 'Quick start' on the breadcrumbs from README.md to quick-start.md
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Add a link to quick-start.md on the "Getting started" section
Since I am not quite sure whether the link to prerequisites.md should be replaced in favor of this link, this commit leaves it as it is for now.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Add a link to quick-start.md on docs/README.md
Since I am not quite sure whether the link to prerequisites.md should be replaced in favor of this link, this commit leaves it as it is for now.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Add note about using "example.com" as an example domain
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Remove backticks from command examples to register a user
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Apply suggestions from code review
Co-authored-by: Slavi Pantaleev <slavi@devture.com>
* Improve notes for instruction to create a user account
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Add details about delegation to installing.md and quick-start.md
Some information is omitted on quick-start.md in favor of installing.md to keep the quick start guide simple.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Update docs/quick-start.md: add the breadcrumb header
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Edit docs/quick-start.md: run the setup command with install-all by default
Refer docs/maintenance-upgrading-services.md
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Revert "Update docs/quick-start.md: add the breadcrumb header"
This reverts commit 9a6e1cf14c7638953fc8fbb8b487ea0afd0a41ad.
As the quick start guide is standalone.
* Update docs/quick-start.md: add headers inside the install section
These headers should make it perfectly clear that there are two steps to be done to install with the playbook
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Update quick-start.md
* Update docs/registering-users.md: notes for manual user registeration
Copy the same notes from quick-start.md
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Reword some things in quick start
* Add alternative to `just roles`
* Update docs/configuring-dns.md: sync with docs/quick-start.md
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Update docs/quick-start.md: add a link to docs/registering-users.md for an instruction to add user accounts
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Update docs/registering-users.md and docs/updating-users-passwords.md: remove "your" from username and password placeholders
These documentations, unlike docs/installing.md and docs/quick-start.md, describe how to handle users (registering them or changing their passwords), some of whom are yours, while others are not.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Update docs/installing.md: add "your" to make it clear that it is "your" account that is going to be created
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Update docs/installing.md and docs/quick-start.md: mention "make roles"
This commit adds mentions to "make roles" and a note about the preference of ansible-playbook commands over the just "recipes".
quick-start.md intends to be referred by those who have never used the playbook to set up a server, so it is safer to regard that it is not clear to them what exactly the just "recipes" are made of, ie. it takes some time and experience until someone understands simplicity of them. For beginners, I believe that we should prefer the basics over simplicity, from the educational point of view.
If someone feels tired of using the same command repetitively, then the person will have been already well accustomed to the way how the playbook works and how the server is supposed to be maintained, and the person is "qualified" to use the just "recipes", and should be able to use them with confidence, distinguishing the playbook tags from the "recipes", for example, from "just install-all" and "ansible-playbook -i inventory/hosts setup.yml --tags=install-all". Such level of familiarity and experience should not be expected on the quick start guide.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Update instructions to update Ansible roles
Also: move the detailed explanation about "just roles" from installing.md to maintenance-upgrading-services.md
TBD: create a dedicated documentation for the "just" program and the concept of its "recipe" (shortcut of commands)
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Add a note about cases to create multiple accounts/users
Since one of the quick start guide's goals is to set up an own user account, this commit adds the note about creating multiple accounts/users to installing.md and registering-users.md only. It should be fine as registering-users.md is linked from quick-start.md
Also:
- On installing.md and quick-start.md, change instruction from what encourages to select "admin=yes" or "admin=no" to what encourages to use "admin=yes", since your user account will be the sole user on the server, as long as you set up the server by following the documentation
- Remove the link to registering-users.md from quick-start.md as the documentation is already linked above, under the header of the section
- Sync docs/installing.md with other documentation
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Remove a line about setting "admin=yes" to reduce the amount of information
Because quick-start.md is getting longer with much information, it removes the note in favor of the linked registering-users.md documentation. The note is available on installing.md as well, and details about adding user accounts for other people can (and should) be checked on those documentations.
Also, this commit edits lines above these notes to make it clear that your user account will be an administrator of the server.
With this commit, the amount of the information about adding user accounts will be: registering-users.md > installing.md > quick-start.md
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Fix a broken anchor link on docs/installing.md
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Replace repetitive information about upgrading with an anchor link to docs/maintenance-upgrading-services.md
Because details to update/upgrade the Matrix services is not necessary for quick start and the amount of information should be reduced from the viewpoint of maintainability, this commit removes details to update/upgrade from quick-start.md
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Update docs/quick-start.md: add a note about keeping it tidy and simple
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Update docs/maintenance-checking-services.md and docs/quick-start.md: add instruction to use federation tester against the base domain
Per Slavi's suggestion.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Update docs/installing.md and docs/quick-start.md: replace commands to finalize the installation
Per Slavi's suggestion.
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
* Clarify install-matrix-static-files to avoid confusion with install-all; Minor consistency improvements
---------
Signed-off-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
Co-authored-by: Suguru Hirahara <acioustick@noreply.codeberg.org>
Co-authored-by: Slavi Pantaleev <slavi@devture.com>
2024-11-23 07:59:29 +00:00
If you are using Cloudflare DNS, make sure to disable the proxy and set all records to "DNS only". Otherwise, fetching certificates will fail.
2020-03-23 15:13:58 +00:00
2021-03-24 04:05:48 +00:00
## DNS settings for optional services/features
2019-02-05 09:07:08 +00:00
2024-11-17 08:10:40 +00:00
For other services which may need subdomain settings, see the table below and configure the DNS (`CNAME`) records accordingly.
| Used by component | Type | Host | Priority | Weight | Port | Target |
| -------------------------------------------------------------------------------------------------------------------------- | ----- | ------------------------------ | -------- | ------ | ---- | -----------------------------------|
| [Dimension ](configuring-playbook-dimension.md ) integration server | CNAME | `dimension` | - | - | - | `matrix.example.com` |
| [Jitsi ](configuring-playbook-jitsi.md ) video-conferencing platform | CNAME | `jitsi` | - | - | - | `matrix.example.com` |
| [Prometheus/Grafana ](configuring-playbook-prometheus-grafana.md ) monitoring system | CNAME | `stats` | - | - | - | `matrix.example.com` |
| [Go-NEB ](configuring-playbook-bot-go-neb.md ) bot | CNAME | `goneb` | - | - | - | `matrix.example.com` |
| [Sygnal ](configuring-playbook-sygnal.md ) push notification gateway | CNAME | `sygnal` | - | - | - | `matrix.example.com` |
| [ntfy ](configuring-playbook-ntfy.md ) push notifications server | CNAME | `ntfy` | - | - | - | `matrix.example.com` |
| [Etherpad ](configuring-playbook-etherpad.md ) collaborative text editor | CNAME | `etherpad` | - | - | - | `matrix.example.com` |
| [Hydrogen ](configuring-playbook-client-hydrogen.md ) web client | CNAME | `hydrogen` | - | - | - | `matrix.example.com` |
| [Cinny ](configuring-playbook-client-cinny.md ) web client | CNAME | `cinny` | - | - | - | `matrix.example.com` |
| [SchildiChat Web ](configuring-playbook-client-schildichat-web.md ) client | CNAME | `schildichat` | - | - | - | `matrix.example.com` |
| [wsproxy ](configuring-playbook-bridge-mautrix-wsproxy.md ) sms bridge | CNAME | `wsproxy` | - | - | - | `matrix.example.com` |
| [Buscarron ](configuring-playbook-bot-buscarron.md ) helpdesk bot | CNAME | `buscarron` | - | - | - | `matrix.example.com` |
| [rageshake ](configuring-playbook-rageshake.md ) bug report server | CNAME | `rageshake` | - | - | - | `matrix.example.com` |
| [ma1sd ](configuring-playbook-ma1sd.md ) identity server | SRV | `_matrix-identity._tcp` | 10 | 0 | 443 | `matrix.example.com` |
| [Postmoogle ](configuring-playbook-bridge-postmoogle.md )/[Email2Matrix](configuring-playbook-email2matrix.md) email bridges | MX | `matrix` | 10 | 0 | - | `matrix.example.com` |
| [Postmoogle ](configuring-playbook-bridge-postmoogle.md ) email bridge | TXT | `matrix` | - | - | - | `v=spf1 ip4:matrix-server-IP -all` |
| [Postmoogle ](configuring-playbook-bridge-postmoogle.md ) email bridge | TXT | `_dmarc.matrix` | - | - | - | `v=DMARC1; p=quarantine;` |
| [Postmoogle ](configuring-playbook-bridge-postmoogle.md ) email bridge | TXT | `postmoogle._domainkey.matrix` | - | - | - | get it from `!pm dkim` |
### SRV record for ma1sd
To make ma1sd enable its federation features, you need to set up a `_matrix-identity._tcp` SRV record. Don't confuse this with the `_matrix._tcp` SRV record for server delegation. See the table above and [this section ](configuring-playbook-ma1sd.md#adjusting-dns-records ) for values which need to be specified.
2022-10-20 04:34:30 +00:00
When setting up a SRV record, if you are asked for a service and protocol instead of a hostname split the host value from the table where the period is. For example use service as `_matrix-identity` and protocol as `_tcp` .
2019-02-05 09:07:08 +00:00
2024-11-17 08:10:40 +00:00
### MX and TXT records for Postmoogle
2022-09-09 07:47:00 +00:00
2024-11-17 08:10:40 +00:00
To make Postmoogle enable its email sending features, you need to configure MX and TXT (SPF, DMARC, and DKIM) records. See the table above for values which need to be specified.
2024-11-03 20:08:10 +00:00
2024-11-05 13:29:54 +00:00
---------------------------------------------
2024-11-09 18:51:36 +00:00
[▶️ ](getting-the-playbook.md ) When you're done with the DNS configuration and ready to proceed, continue with [Getting the playbook ](getting-the-playbook.md ).
