Skip to content

mx_records_conflict

Existing MX records conflict. HTTP status 409.

The domain has MX records that point to another mail service, which turning on email forwarding would replace. With `force: true` it means the records in `remainingMxRecords` could not be removed.

What to do

To replace them, send PATCH /api/v2/domains/{id}/email-forwarding again with enabled: true and force: true. Mail then stops going to the old service. If remainingMxRecords is set, delete those records with DELETE /api/v2/dns-zones/{id}/records/{recordId}, then turn forwarding on again.

What the message says

  • Non-Cloudflare MX records exist for this domain. Enabling email forwarding will replace them.

Example

Response 409
{
"type": "https://developer.hostup.se/errors/mx_records_conflict",
"title": "Existing MX records conflict",
"status": 409,
"detail": "Non-Cloudflare MX records exist for this domain. Enabling email forwarding will replace them.",
"code": "mx_records_conflict",
"requestId": "req_01hxa3b4c5d6e7f8g9h0j1k2m3"
}

Branch on code, not on title or detail. When you contact support about it, include the requestId. More in Errors and retries.

Endpoints that return it