How to Set Up OVHcloud DNS Records for Email Marketing

You manage DNS records in OVHcloud through the DNS zone tab in the Web Cloud section of the control panel. OVHcloud uses a step-by-step wizard to create records and defaults to a TTL of 3600 seconds (1 hour). When configuring external email marketing services, two specific requirements stand out: you must leave the Sub-domain field blank for root records, and you must add a trailing dot to external CNAME target hostnames.

OVHcloud DNS navigation and nameserver check

To access your DNS zone in OVHcloud:

1. Log in to the OVHcloud Control Panel.
2. In the top navigation bar, click Web Cloud.
3. In the left menu, expand Domain names and select your domain.
4. Click the DNS zone tab.

Before adding records, click the DNS servers tab next to DNS zone. Verify that your domain points to OVHcloud nameservers (such as dns10.ovh.net and ns10.ovh.net). If your domain uses custom nameservers pointing to an external host, records created in OVHcloud will not publish to the internet. Configure your records in that external DNS dashboard instead.

Adding a record in OVHcloud

1. On the DNS zone tab, click Add an entry.
2. Select the record type from the list (TXT, CNAME, or MX).
3. Fill in the Sub-domain field:
   • For root domain records (such as SPF), leave the Sub-domain field blank. OVHcloud does not accept @ for root records.
   • For subdomains (such as _dmarc or DKIM selectors), enter only the prefix. OVHcloud appends your root domain automatically.
4. Enter the destination value:
   • For TXT records, enter the string in the Value box. Do not wrap the value in quotation marks.
   • For CNAME records, enter the target hostname in the Target field. Append a trailing dot (.) to external hostnames (for example, s1.domainkey.example-esp.com.).
   • For MX records, enter your priority integer in the Priority field, and enter the mail server hostname in the Target field.
5. Leave the TTL field at its default setting.
6. Click Next, then review the details and click Confirm.

OVHcloud outlines its DNS zone management tools in its DNS zone editing guide.

Required authentication records

Receiving mail servers use these three records to verify that messages sent from your domain are authentic.

1. SPF (Sender Policy Framework)

• Record type: TXT
• Sub-domain: Leave blank
• Value: The SPF string provided by your email platform, such as:

  v=spf1 include:_spf.google.com include:sendgrid.net ~all

• TTL: Default

OVHcloud includes a legacy “SPF” record option in its record type list. Modern mail servers evaluate SPF exclusively through standard TXT records. Always choose the TXT record type.

Merging multiple SPF records

A domain must only have one root SPF record. If you use OVHcloud Hosted Exchange, Zimbra, or MX Plan, an SPF record may already exist in your DNS zone (v=spf1 include:mx.ovh.com ~all).

Do not add a second TXT record starting with v=spf1. Multiple SPF records cause receiving mail servers to fail evaluation with a PermError, routing messages to spam or blocking them entirely.

To update an existing SPF record:

1. In the DNS zone table, search for TXT records.
2. Find the existing record starting with v=spf1, click the three-dots icon on the right, and select Modify the entry.
3. Add your email marketing provider’s include: mechanism before the closing qualifier (~all or -all). For example:

   v=spf1 include:mx.ovh.com include:sendgrid.net ~all

4. Click Next, then click Confirm.

Do not add quotation marks around the string in the Value field. OVHcloud formats the record automatically.

2. DKIM (DomainKeys Identified Mail)

Email providers supply DKIM records in either CNAME or TXT format:

CNAME-based DKIM

Most modern email platforms (such as Klaviyo, Postmark, SendGrid, and Amazon SES) use CNAME records:

• Record type: CNAME
• Sub-domain: The selector prefix without your domain, such as s1._domainkey
• Target: The destination hostname ending with a trailing dot, such as s1.domainkey.example-esp.com.
• TTL: Default

OVHcloud requires a trailing dot on external hostnames. If you omit the dot, OVHcloud appends your domain name, creating s1.domainkey.example-esp.com.yourdomain.com..

TXT-based DKIM

Some platforms provide a raw public key string:

• Record type: TXT
• Sub-domain: The selector prefix, such as google._domainkey
• Value: The raw public key string starting with v=DKIM1; k=rsa; p=...
• TTL: Default

Paste the public key string into the Value field without quotation marks.

3. DMARC (Domain-based Message Authentication, Reporting, and Conformance)

• Record type: TXT
• Sub-domain: _dmarc (OVHcloud appends your domain name automatically)
• Value:

  v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com; pct=100;

• TTL: Default

Start with p=none to collect delivery reports without affecting message flow. Once SPF and DKIM authenticate consistently across all your sending services, update the policy tag to p=quarantine or p=reject.

Optional deliverability and branding records

These records configure custom subdomains for bounce handling and link tracking.

4. Custom return path (bounce domain) (optional)

• Record type: CNAME
• Sub-domain: bounces (or the subdomain prefix specified in your platform settings)
• Target: The mail server hostname ending with a trailing dot (such as pm.mtasv.net.)
• TTL: Default

5. Branded tracking domain (optional)

• Record type: CNAME
• Sub-domain: links (or track, click, or email as specified by your platform)
• Target: The tracking hostname ending with a trailing dot
• TTL: Default

Setting up custom MX records (if required)

If your email marketing service requires dedicated MX records for inbound message processing, reply handling, or sending subdomains:

1. Click Add an entry and choose MX.
2. Enter the details:
   • Sub-domain: Leave blank for the root domain, or enter mail for a dedicated sending subdomain.
   • Priority: The integer specified by your provider (such as 10).
   • Target: The mail server address provided by your platform (such as feedback-smtp.us-east-1.amazonses.com.). Include a trailing dot.
   • TTL: Default
3. Click Next, then click Confirm.

If you use OVHcloud Hosted Exchange, MX Plan, or Google Workspace for your business mailboxes, do not overwrite your root MX records. Replacing root MX records pointing to OVHcloud servers (mx1.mail.ovh.net, etc.) halts incoming email for your organization. Only add MX records for dedicated subdomains unless you are switching your primary email system.

Verifying your DNS records

OVHcloud zone updates usually propagate within a few hours. You can verify your DNS records in Windows PowerShell using Resolve-DnsName:

Check SPF

Resolve-DnsName -Name yourdomain.com -Type TXT

Review the Strings column. Verify that only one SPF record exists and that your sending service mechanism is listed.

Check DMARC

Resolve-DnsName -Name _dmarc.yourdomain.com -Type TXT

Confirm that the output contains your v=DMARC1; p=... record.

Check DKIM

Replace s1 with your provider’s specific selector:

Resolve-DnsName -Name s1._domainkey.yourdomain.com -Type CNAME

If your platform uses TXT-based DKIM, change -Type CNAME to -Type TXT. The output will display your provider’s target hostname or public key.

Check tracking and bounce records (if configured)

Resolve-DnsName -Name bounces.yourdomain.com -Type CNAME

The NameHost column should point to your email platform’s destination address.

Check MX records (if configured)

Resolve-DnsName -Name yourdomain.com -Type MX

The NameExchange column should list your designated mail servers with their numerical priorities under Preference.

Common troubleshooting issues

Issue	Root cause	Solution
CNAME destination is duplicated (target.com.yourdomain.com.)	The target hostname was entered without a trailing dot.	Add a period to the end of the destination hostname in the Target field (such as target.com.).
Subdomain hostname is duplicated (_dmarc.yourdomain.com.yourdomain.com)	The full domain was typed into the Sub-domain field.	Enter only the subdomain prefix (such as _dmarc). OVHcloud appends your domain automatically.
SPF status shows PermError	Multiple TXT records start with v=spf1.	Edit the existing SPF record, merge all include: mechanisms into that single record, and delete any duplicate entries.
Root record fails to save	An @ symbol was entered into the Sub-domain field.	Leave the Sub-domain field blank. OVHcloud uses blank inputs to designate the root domain.
OVHcloud business email stops working	Root MX records pointing to OVHcloud servers were replaced.	Restore the original OVHcloud MX records, and configure marketing MX records on a dedicated sending subdomain.
Records do not resolve externally	The domain uses external nameservers.	Check the DNS servers tab in the OVHcloud dashboard. If custom nameservers are active, configure DNS records at that external provider.