eusend
DomainsDNS Providers

OVHcloud

Publish your eusend DNS records in an OVHcloud DNS zone — the trailing dot that decides whether your MX record works, and the record types to avoid picking.

OVHcloud has one rule that matters more than anything else here: a target without a trailing dot gets your own domain appended to it.

Add the records

Open the DNS zone

In the OVHcloud Control Panel, go to Web CloudDomain names, select your domain, and open the DNS zone tab. Click Add an entry above the table.

DKIM — required

Choose TXT as the entry type.

FieldValue
Subdomaineusend._domainkey
TTLBy default
Valuethe full v=DKIM1; k=rsa; p=… value from the dashboard

Click Next, then Confirm.

OVH's type list also offers dedicated DKIM and SPF entries, which build the record from separate fields instead of one value. Plain TXT is what these instructions assume and is the simpler path — you already have the finished value.

FieldValue
TypeTXT
Subdomain_dmarc
Valuev=DMARC1; p=none; rua=mailto:dmarc@acme.com

Use an address you actually read for rua — see DMARC.

Return-Path — optional, both or neither

FieldValue
TypeTXT
Subdomainsend
Valuev=spf1 include:_spf.eusend.dev ~all

Then the MX record — and mind the dot:

FieldValue
TypeMX
Subdomainsend
Priority10
Targetfeedback.eusend.dev.

Publish both and eusend switches your mail to a bounce address on your own domain, so SPF passes and aligns. One without the other does nothing.

OVHcloud specifics

The trailing dot on the MX target is not optional. OVH's documentation: when the target is a domain, "punctuate it. Otherwise, your domain name gets appended to the target." Enter feedback.eusend.dev without the final dot and OVH stores feedback.eusend.dev.acme.com, which does not exist — bounces then go nowhere and SPF alignment never switches on.

The Subdomain field takes the subdomain only. eusend._domainkey, _dmarc, send. Leave it empty for the root domain. OVH adds your domain when it writes the record, the same way it does to an unpunctuated target.

TTL. Leave it on By default, or pick Customised and set a value in seconds. There is no reason to change it for these records.

Never use "Reset the DNS zone". The button sits near the zone editor and restores OVH's default records, deleting everything you added — including your DKIM record. If you are trying to fix one bad record, edit that row instead: open the menu on it and choose Edit the entry.

Only when the domain uses OVH's nameservers. If the Server tab shows nameservers elsewhere, the DNS zone tab here is not what the internet reads.

Propagation. OVH's own documentation allows up to 24 hours. In practice it is much faster, but it is the slowest provider in this list to promise anything.

Check it

verify
dig +short TXT eusend._domainkey.acme.com
dig +short MX send.acme.com

The second command should print 10 feedback.eusend.dev. — if it prints feedback.eusend.dev.acme.com., the trailing dot is missing from the target.

Official documentation: Editing an OVHcloud DNS zone and How to add a DNS TXT record.