leafleafleafDocy banner shape 01Docy banner shape 02Man illustrationFlower illustration

Set up your domain for UltaMail

To use your domain with UltaMail, add the email records in your DNS provider’s control panel. MX records route incoming mail. SPF, DKIM and DMARC help receiving servers check messages sent from your domain.

Before you start

Have your UltaMail login and DNS access ready. Edit the DNS zone used by your domain’s active nameservers, even if you bought the domain or host your website elsewhere.

Set up the domain and mailbox in UltaMail before changing MX records. DNS records do not create mailboxes or transfer existing messages.

If you are moving from another provider, save its DNS records and back up your messages first. Keep the old service active during the move. New MX records redirect incoming mail, but messages already in the old mailbox stay there.

If possible, lower the existing MX records’ TTL a day before the move. Keep the old mailboxes available until the transfer and delivery checks are complete.

1. Add the MX records

Add these four MX records at the root domain. Set priority to 10 and TTL to 3600 seconds for each record.

TypeNamePriorityMail serverTTL
MX@10mx001.cloudeu.xion.oxcs.net3600
MX@10mx002.cloudeu.xion.oxcs.net3600
MX@10mx003.cloudeu.xion.oxcs.net3600
MX@10mx004.cloudeu.xion.oxcs.net3600

Your provider may use @, a blank hostname or the domain name for the root domain. Enter each mail server exactly as shown, without https:// or a path. These are the mail provider’s servers. You do not need to create these hostnames in your own zone.

When you are ready to switch, replace the old provider’s MX records. Keep records for another mail provider only if your mail administrator has configured them to work together.

2. Set up SPF

If UltaMail is your only sending service, add a TXT record with name @, TTL 3600 and this value:

v=spf1 include:spf.cloudeu.oxcs.net ~all

If you already have an SPF record, update it. Do not create a second SPF policy at the same name. Keep the authorizations needed by any website, CRM or other service that sends mail for your domain.

Add UltaMail’s include to that policy rather than pasting in a second complete policy. Check the combined record’s syntax and DNS lookup limit before saving.

3. Configure DKIM

Open Domain Settings in the UltaMail dashboard. Use the Automatic Configuration Wizard to get the DNS records for your exact domain. If you enter them yourself, add both DKIM records as CNAMEs at your authoritative DNS provider.

These are the two records for example.com. Copy the targets from your own dashboard when setting up a real domain.

  • First CNAME
    Name: oc-rsa-selector1._domainkey
    Target: oc-rsa-selector1-example-com._domainkey.oxcloud.zone.
  • Second CNAME
    Name: oc-rsa-selector2._domainkey
    Target: oc-rsa-selector2-example-com._domainkey.oxcloud.zone.

Some DNS providers append your domain to the record name automatically. In that case, enter only the name shown above. The targets point to oxcloud.zone and must match the values supplied for your domain.

After both CNAMEs are visible, return to Domain Settings and use the control in the DKIM section to generate and activate the key. Then send a test message to Gmail and open Show original to check for DKIM: PASS and an oc-rsa-selector selector for your domain.

4. Set up DMARC

Check for an existing TXT record at _dmarc. If you find one, keep its policy and reporting settings unless your mail administrator approves a change. Publish only one DMARC record at that name.

If there is no DMARC record, the UltaMail setup uses this TXT value:

v=DMARC1; p=quarantine

For this example, use type TXT, name _dmarc and TTL 3600. The p=quarantine policy asks receiving mail systems to treat messages that fail DMARC as suspicious, usually by putting them in spam. This example has no reporting address. To receive reports, add a rua address for a mailbox or reporting service you control and have set up to accept them.

Keep any existing reporting settings or stronger policy unless a change has been agreed. Before changing enforcement, check that your legitimate senders pass authentication and domain alignment checks.

5. Enter the records in your DNS provider

Cloudflare

  1. Select your domain and open DNS > Records.
  2. Add the four MX records. Add or update the SPF and DMARC TXT records using the values above. Use @ for the root domain and _dmarc for DMARC.
  3. Add both DKIM CNAME records from UltaMail and set them to DNS only.
  4. Set any A, AAAA or CNAME record used only for mail to DNS only (the gray cloud). MX and TXT records are already DNS-only and have no proxy switch. Leave the website’s proxy settings alone unless its configuration requires a change.
  5. Review the saved names and values. If Cloudflare Email Routing controls the current MX records, resolve that conflict before switching to UltaMail.

Bunny DNS

  1. Open DNS in your bunny.net dashboard and select the active zone.
  2. Choose Add Record and add each MX record with priority 10 and TTL 3600. Leave the hostname blank for the root domain.
  3. Add or update the SPF and DMARC TXT records. Leave the SPF hostname blank and use _dmarc for DMARC. Enter the values above and set TTL to 3600.
  4. Add both DKIM records as CNAME records using the names and targets from UltaMail.
  5. Keep CDN Acceleration off for hostnames used only for mail, where the option is available. Keep the DNS records enabled. Do not use a Pull Zone record for email. You do not need to change website acceleration settings to add MX or TXT records.

6. Check DNS and test delivery

  1. Save the records at your authoritative DNS provider. Other servers may keep the old records cached until their TTL expires.
  2. Run UltaMail’s domain check. Check all four MX destinations, both DKIM CNAMEs and one SPF and one DMARC policy at their respective names.
  3. Send a message from your UltaMail mailbox to an external address, then reply from that address. During a migration, check the old mailbox too. Some messages may still arrive there while old MX records remain cached.
  4. Check the authentication results in the external message’s headers. A successful DNS check does not confirm that every sender is configured correctly or guarantee inbox delivery. Finish both DKIM records and the authentication checks before treating setup as complete.

Troubleshooting

  • Records are missing: check that you edited the zone used by the domain’s active nameservers.
  • Mail still reaches the old provider: check for old MX records and allow cached records to expire.
  • SPF fails: look for duplicate SPF policies, missing sending services or DNS lookup-limit errors.
  • DMARC fails: check the record name and syntax, then check authentication and alignment with the message’s From domain.
  • Delivery still fails: send support the affected domain and the error or bounce message. Never send mailbox passwords or private signing keys.

DNS provider documentation

See Cloudflare’s email DNS documentation or the Bunny DNS records guide for more on the controls in each dashboard.

Share this Doc

Set up your domain for UltaMail

Or copy link

Table Of Contents