DNS Providers

The records eusend gives you are the same everywhere. What differs is what each control panel expects you to type into its fields — and getting that wrong is the reason most domains fail to verify.

Pick your provider below, or read the four traps first if yours is not listed.

Which guide do I need?

Not your registrar — your DNS host. If you bought the domain at Namecheap but moved it to Cloudflare's nameservers, the records go in Cloudflare and the Namecheap panel will do nothing. Ask your domain who is in charge:

dig +short NS acme.com

The answer names the provider whose guide you want. If it is a host with no guide here, the four traps cover everything you need — the field labels are the only thing that changes.

The four traps

1. The Host field almost never wants your domain

Most panels append your domain to whatever you type. eusend shows you the full record name, eusend._domainkey.acme.com, because that is what has to exist in DNS — but pasting all of it into a field that appends gives you eusend._domainkey.acme.com.acme.com, which resolves to nothing.

In those panels you enter eusend._domainkey and stop. Each guide below says exactly what its panel does.

To check whether this is what went wrong:

dig +short TXT eusend._domainkey.acme.com.acme.com

An answer here means the record exists at the wrong name. Edit the record and remove the domain from the Host field.

2. The root domain is spelled differently everywhere

@, blank, or the domain itself, depending on the panel. This only matters for DMARC if you are publishing it at the apex — the eusend records all sit on subdomains (eusend._domainkey, _dmarc, send), so you will usually not need it.

3. The DKIM value is longer than a single DNS string may be

A single string in a TXT record may hold 255 characters. Your DKIM value is around 400, because a 2048-bit RSA public key is long. The record is therefore stored as two strings, and resolvers join them back together — this is normal DNS, not a workaround.

Most panels do the splitting for you when you paste the value whole. Two in this list do not: Route 53 and Gandi expect you to split it yourself and wrap each piece in double quotes. Their guides show how.

If a panel rejects your value as too long, that is what it is asking for. Never shorten or truncate the key — DKIM breaks.

4. MX targets sometimes need a trailing dot

The optional Return-Path MX record points at feedback.eusend.dev. Some panels — OVHcloud notably — append your own domain to any target that does not end in a dot, turning it into feedback.eusend.dev.acme.com. Where that is the case the guide says to type feedback.eusend.dev. with the dot.

What you are publishing

Only the first record is required. The full reasoning for each — including why there is deliberately no SPF record on your root domain — is in DNS records.

After you save

Publishing is all you have to do — eusend polls your DNS in the background and flips the domain to verified on its own. If you want to check the records yourself first:

dig +short TXT eusend._domainkey.acme.com
dig +short TXT _dmarc.acme.com