|
| 1 | +--- |
| 2 | +title: How to authenticate your sending domain with Transactional Email |
| 3 | +description: Guide to authenticating your domain for Scaleway Transactional Email. |
| 4 | +tags: transactional sending-domain sending domain managed-services |
| 5 | +dates: |
| 6 | + validation: 2025-10-01 |
| 7 | + posted: 2025-10-01 |
| 8 | +--- |
| 9 | +import Requirements from '@macros/iam/requirements.mdx' |
| 10 | +import image2 from './assets/scaleway_dkim_name_value.webp' |
| 11 | + |
| 12 | +This page shows you how to manually configure your sending domain's DNS records to authenticate the domain and start sending [transactional emails](/transactional-email/concepts/#transactional-email). |
| 13 | + |
| 14 | +<Message type="tip"> |
| 15 | + You can [set up autoconfiguration](/transactional-email/how-to/autoconfigure-domain) for your TEM domain. |
| 16 | +</Message> |
| 17 | + |
| 18 | +<Requirements /> |
| 19 | + |
| 20 | +- A Scaleway account logged into the [console](https://console.scaleway.com) |
| 21 | +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization |
| 22 | +- [Configured a domain name](/transactional-email/how-to/configure-domain-with-transactional-email) for Transactional Email |
| 23 | + |
| 24 | +1. Click **Transactional Email** in the **Domains & Web Hosting** section of the [console](https://console.scaleway.com/) side menu. The **Transactional Email** overview page displays. |
| 25 | +2. Click the name of the email domain you want to authenticate. The domain overview page displays. You can see the status of the DNS records. |
| 26 | +3. Click the **DNS records** tab. |
| 27 | + |
| 28 | +On this tab, you can configure: |
| 29 | + - **SPF record** – Authorizes specific mail servers to send emails on behalf of your domain, preventing unauthorized use. |
| 30 | + - **DKIM record** – Adds a digital signature to verify email integrity and confirms it was sent from your domain. |
| 31 | + - **DMARC record** – Defines how receiving servers should handle authentication failures and enables reporting for your domain. |
| 32 | + - **MX record** – Directs incoming emails to your mail server but is not involved in sending or authenticating outgoing emails. |
| 33 | + |
| 34 | +<Message type="important"> |
| 35 | +Keep in mind that: |
| 36 | + - The verification of your domain might take up to 48 hours. |
| 37 | + - Scaleway performs regular validity checks on your domain that can impact its validity. |
| 38 | +</Message> |
| 39 | + |
| 40 | +## How to configure SPF records |
| 41 | + |
| 42 | +1. Scroll to the SPF, DKIM and DMARC records section. |
| 43 | +2. Copy the value that applies to your case to add an SPF record. |
| 44 | + |
| 45 | + <Message type="important"> |
| 46 | + - If you have no SPF record on this domain, copy the following value: `v=spf1 include:_spf.tem.scaleway.com -all` |
| 47 | + - If you already have configured an SPF record, copy the following value: `include:_spf.tem.scaleway.com` |
| 48 | + </Message> |
| 49 | + |
| 50 | +3. Add a `TXT` record type in the same zone as your Transactional Email's domain, on your DNS zone. |
| 51 | +4. Paste the value you have copied in the **Value** section. |
| 52 | +5. Save your changes. |
| 53 | + |
| 54 | +## How to configure DKIM records |
| 55 | +1. Scroll to the SPF, DKIM and DMARC records section. |
| 56 | +2. Copy the value that applies to your case to add an DKIM record. |
| 57 | +3. Add a `TXT` record type in the same zone as your Transactional Email's domain, on your DNS zone. |
| 58 | +4. Copy the name that displays in the console and past it in the **Name** field. |
| 59 | +5. Copy the value that displays in the console and paste it in the **Value** section. |
| 60 | + <Lightbox image={image2} alt="" /> |
| 61 | +6. Save your changes. |
| 62 | + |
| 63 | +## How to configure DMARC records |
| 64 | + |
| 65 | +1. Add a `TXT` record type in the same zone as your Transactional Email's domain, on your DNS zone. |
| 66 | +2. Enter `_dmarc` in the **Name** field, followed by the domain name. For example, if your domain is called `my-domain.com`, you should have `_dmarc.my-domain.com.` in the **Name** field. |
| 67 | +3. Enter your desired tags and their values in the **Value** section. Make sure that you add the mandatory `v` and `p` tags, and that you separate tags from each other with semi-colons. Find out about DMARC configuration in our [dedicated documentation](/transactional-email/reference-content/dmarc-configuration/). |
| 68 | + Your **Value** field should look similar to the following: |
| 69 | + ``` |
| 70 | + v=DMARC1; p=none; rua=mailto:[email protected] |
| 71 | + ``` |
| 72 | + <Message type="important"> |
| 73 | + It is possible to configure several DMARC records for one domain, but they must have different names to be valid. |
| 74 | + For example, the `_dmarc.mydomain.com` and `_dmarc.tem.mydomain.com` DMARC records are valid. |
| 75 | + </Message> |
| 76 | +4. Confirm the changes and add the DMARC record. |
| 77 | + |
| 78 | + <Message type="tip"> |
| 79 | + If you have a domain at Scaleway Domains and DNS, you can access your account from the Scaleway [console](https://console.scaleway.com/), click **Domains and DNS** > **Your domain** > **DNS Zones**, then add a record in the same zone as your Transactional Email's domain. |
| 80 | + </Message> |
| 81 | + |
| 82 | +## How to configure MX records |
| 83 | + |
| 84 | +<Message type="important"> |
| 85 | + We recommend you use your own MX server if you have one. If you do not have an MX server, we recommend you use Scaleway's blackhole MX, as it allows you to avoid email rejection. However, this also means that the emails sent back to the Scaleway blackhole MX will be lost and unrecoverable. |
| 86 | +</Message> |
| 87 | + |
| 88 | +1. Add an [MX record](/transactional-email/concepts/#mx-record) type in the root zone of your domain on your DNS zone. |
| 89 | +2. Enter a name of your choice in the **Name** field. |
| 90 | +3. Set `10` as a [priority](/transactional-email/concepts/#priority) for your MX record. |
| 91 | + <Message type="note"> |
| 92 | + Priority indicates the order in which your mail servers should be tried by a mail server that is attempting to deliver emails. |
| 93 | + </Message> |
| 94 | +4. Enter the name of your MX followed by a trailing dot in the **Hostname** field. |
| 95 | +5. Save your changes. |
| 96 | + |
| 97 | +### How to add Scaleway's MX record |
| 98 | + |
| 99 | +<Message type="important"> |
| 100 | + - Scaleway provides its own MX server to improve email deliverability. <br /> However, Scaleway's MX server is a **blackhole**. This means that **any email sent back to it will be lost with no possibility of recovery**. |
| 101 | + - If you have no MX server, we recommend you use Scaleway's blackhole MX to avoid getting your emails rejected. |
| 102 | +</Message> |
| 103 | + |
| 104 | +1. Add an [MX record](/transactional-email/concepts/#mx-record) type in the root zone of your domain on your DNS zone. |
| 105 | +2. Enter a name of your choice in the **Name** field. |
| 106 | +3. Set `10` as a [priority](/transactional-email/concepts/#priority) for your MX record. |
| 107 | + <Message type="note"> |
| 108 | + Priority indicates the order in which your mail servers should be tried by a mail server that is attempting to deliver emails. |
| 109 | + </Message> |
| 110 | +4. Enter `blackhole.tem.scaleway.com.` in the **Hostname** field. Make sure you add the trailing dot at the end of the value. |
| 111 | +5. Save your changes. |
0 commit comments