How to Set Up DMARC in OVH: Step-by-Step DNS Configuration

OVH (now OVHcloud) is one of Europe's largest hosting and cloud infrastructure providers, serving millions of customers across more than 30 countries. If your domain is registered or hosted with OVH, adding a DMARC record is a straightforward task through the OVH Control Panel. For EU-based businesses particularly, having proper email authentication in place strengthens both your security posture and your alignment with data protection expectations under GDPR — ensuring that emails sent on behalf of your domain are legitimate and traceable.

This guide walks you through adding a DMARC TXT record in the OVH Control Panel (Manager), configuring SPF and DKIM if you use OVH email hosting, and verifying the record is live. If you have not built your DMARC record yet, start with our how to create a DMARC record guide.

Before You Start

Make sure you have these things ready:

Your DMARC record value. A good starting record for monitoring looks like:

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

Start with p=none to collect reports before enforcing anything. You can upgrade your policy later once you have confirmed all your legitimate email passes authentication. See our DMARC policy levels guide for the full breakdown.

Access to the OVH Control Panel. You need to be the account owner or an authorized contact with DNS management permissions. Log in at ovh.com to reach the OVH Manager dashboard.

SPF and DKIM already configured. DMARC depends on SPF and DKIM working correctly. If you use OVH email hosting (MX Plan or Email Pro), check your DNS zone for existing SPF and DKIM entries. If you use a third-party email provider, make sure those authentication records are in place first.

Step-by-Step: Adding DMARC in OVH

SPF and DKIM on OVH

DMARC checks whether SPF or DKIM passes and aligns with your From address. Both should be configured before you enforce your DMARC policy. For a detailed comparison of how these protocols work together, see SPF vs DKIM vs DMARC.

SPF for OVH Email

If you use OVH email hosting (MX Plan, Email Pro, or Exchange), OVH typically creates a default SPF record when you activate the email service. Check your DNS zone for a TXT record starting with v=spf1. It usually looks something like:

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

If you also send email through other services (Google Workspace, Mailchimp, SendGrid, etc.), you need to include those in your SPF record as well. Build a comprehensive SPF record at spfcreator.com that covers all your sending sources. Be careful not to exceed the ten DNS lookup limit for SPF.

DKIM for OVH Email

OVH supports DKIM for its email hosting services. Depending on your plan (MX Plan, Email Pro, or Hosted Exchange), you may need to enable DKIM manually through the OVH Manager under your email service settings. Once enabled, OVH publishes the necessary DKIM DNS records automatically in your zone file.

If you use a third-party email provider alongside OVH hosting, you need to set up DKIM for that provider separately. Add the DKIM CNAME or TXT records provided by your email service to the OVH DNS zone. You can generate DKIM records at dkimcreator.com.

Common OVH Email Setups

Your DMARC configuration depends on how you send email. Here are the typical OVH scenarios:

Using OVH MX Plan or Email Pro Only

If OVH is your sole email provider, make sure your SPF record includes OVH servers (include:mx.ovh.com) and DKIM is enabled in your email service settings. This is the simplest scenario — one provider, one set of authentication records.

Using Google Workspace or Microsoft 365

If you use a third-party email provider but manage DNS through OVH, you need:

• An SPF record that includes your email provider (for example, include:_spf.google.com for Google Workspace)
• DKIM records from your email provider added to the OVH DNS zone
• MX records pointing to your email provider (these should already be set if email is working)

Remove or update any OVH-specific email SPF entries if you are no longer using OVH email. Having unused SPF includes will not break DMARC, but keeping your SPF record clean reduces the risk of hitting lookup limits.

Using OVH Email and a Marketing Platform

If you use OVH for day-to-day email and a platform like Mailchimp, Brevo, or Klaviyo for marketing campaigns, your SPF record needs to include both services. Each service also needs its own DKIM setup. This is the most complex scenario and the most important one to get right before enforcing DMARC.

GDPR and Email Authentication for EU Businesses

As a major European provider, OVH is a popular choice for businesses that want to keep infrastructure within the EU. While GDPR does not explicitly require DMARC, the regulation's emphasis on data integrity and protection of personal information makes email authentication a practical priority. Spoofed emails sent from your domain can lead to phishing attacks that compromise customer data — a situation that could trigger GDPR incident reporting obligations. Implementing DMARC with SPF and DKIM demonstrates that your organization takes reasonable technical measures to protect outbound communications and the personal data of your contacts.

Verifying Your DMARC Record

After saving the record in OVH, wait a few hours and then check it at dmarcrecordchecker.com. Enter your domain and verify:

• The record starts with v=DMARC1
• Your chosen policy is present
• The rua reporting address is correct if you included one
• There is only one DMARC record (no duplicates)

If the record does not appear after 24 hours, double-check that your domain's nameservers are managed by OVH. You can verify this in the DNS Servers tab of your domain management page. If nameservers point elsewhere, add the record at that DNS provider instead.

Troubleshooting OVH DNS Issues

Record Not Appearing

The most common causes are:

• Nameserver mismatch. If your nameservers point to another provider like Cloudflare, records added in OVH will not resolve publicly.
• Typo in the subdomain. The subdomain field must be _dmarc with the underscore. Even a small typo puts the record in the wrong location.
• Propagation delay. OVH's default TTL means changes can take up to 24 hours to propagate globally. Give it time before troubleshooting further.

Updating Your Record Later

When you are ready to move from monitoring to enforcement, find your DMARC TXT record in the OVH DNS zone and click the pencil icon to edit. Update the policy value and save. Start with p=quarantine; pct=25; and increase gradually. For the full enforcement path, see our DMARC policy levels guide.

Monitor Your DMARC Record

You've created your DMARC record — now make sure it keeps working. The Email Deliverability Suite watches your SPF, DKIM, DMARC, and MX records daily and alerts you when something breaks.