How do you set up DMARC on OVHcloud?

Updated July 3, 2026

To set up DMARC on OVHcloud, open the control panel, go to Web Cloud → Domain names, select your domain, open the DNS zone tab, and add a TXT entry with subdomain _dmarc and a value starting with v=DMARC1. OVH applies zone changes within minutes, though caching can delay visibility up to a few hours.

What you need before starting

  • An OVHcloud account with the domain using OVH's DNS servers (check the DNS servers tab; if it points elsewhere, edit DNS there)
  • A DMARC record value (generate one with our free DMARC generator if you don't have one yet)
  • Optional but recommended: SPF and DKIM already configured for your email provider

Step by step

  1. 1

    Open your domain's DNS zone

    Sign in to the OVHcloud control panel, open Web Cloud in the top menu, expand Domain names in the left sidebar, click your domain, and open the DNS zone tab.

  2. 2

    Add a new entry

    Click Add an entry, then choose TXT from the list of record types (OVH's wizard also offers dedicated SPF and DKIM helpers; for DMARC, plain TXT is what you want).

  3. 3

    Enter the DMARC record

    In the Sub-domain field enter _dmarc. OVH shows .yourdomain.com after the field and appends it automatically. Paste your DMARC record into the Value field and confirm.

    Host _dmarcType TXT
    v=DMARC1; p=none; rua=mailto:[email protected]; fo=1
  4. 4

    Confirm and apply the change

    Review the summary and click Confirm. OVH regenerates the zone within minutes; cached resolvers may take up to the zone's TTL (often an hour or more) to see it.

  5. 5

    Verify it's live

    Run your domain through our free DMARC checker. If the record shows up and parses cleanly, you're done. The first aggregate reports typically arrive within 24-48 hours.

Check that it worked

Our free checker reads your DMARC record live and explains every tag. Run it after the record saves.

Open the DMARC checker →

Common mistakes

Editing the zone while the domain uses external DNS servers

The DNS zone tab only matters if the DNS servers tab lists OVH's nameservers. If you delegated to Cloudflare or elsewhere, the OVH zone is ignored. Add the record at the active host.

Adding a second DMARC record instead of editing the first

OVH's email offers (MX Plan, Email Pro, Hosted Exchange) sometimes come with pre-filled authentication entries. Filter the zone for _dmarc and edit any existing TXT record rather than duplicating it.

Putting the record in the wrong zone after a subdomain delegation

If you delegated subdomains to separate zones, make sure _dmarc is added in the root domain's zone. Receivers query _dmarc.yourdomain.com, not a subdomain's zone.

Frequently asked questions

OVH's wizard has SPF and DKIM options. Is there a DMARC one?
OVH's guided entries cover SPF and DKIM; DMARC is added as a standard TXT entry with sub-domain _dmarc, exactly as shown above. Newer panels may offer a DMARC helper, but the TXT route always works.
How long does an OVH DNS zone change take?
OVH regenerates its zone within a few minutes of confirming. Visibility elsewhere depends on the record's TTL. Allow an hour or two before troubleshooting.
Does this cover OVH Hosted Exchange or Email Pro?
Yes. DMARC is per domain, so one _dmarc record covers all OVH email products on that domain. Just make sure SPF and DKIM are configured for the product you use.

The record is step one. The reports are the point

Publishing p=none starts a stream of XML reports about everyone sending as your domain. DMARCPath turns them into a plain-English dashboard and walks you to full protection at p=reject. One domain free.

Monitor this domain free →