What is an MX Record?
An MX (Mail Exchanger) record tells the internet where to deliver incoming email for a domain. Each MX record has a priority value — the lower the number, the higher the priority. For example, if you use Google Workspace, you likely have an MX record like this:anyone@yourdomain.com gets delivered to Google’s mail servers.
Will the Flowforth MX Record Conflict?
No. The MX record Flowforth asks you to add is on a subdomain (e.g.,send.yourdomain.com), not your root domain. It looks something like this:
send.yourdomain.com and yourdomain.com are separate, the Flowforth MX record has no impact on where your regular email gets delivered.
Your existing email (Google Workspace, Microsoft 365, etc.) will continue to work exactly as before.
Common Conflicts and How to Solve Them
Conflicting Record on the Same Subdomain
If you already have an MX record set forsend.yourdomain.com from a different service, you’ll need to remove it before adding the Flowforth MX record.
Alternatively, you can use a different subdomain when adding your domain to Flowforth (e.g., mail.yourdomain.com instead of send.yourdomain.com).
Conflicting Priority Values
Each MX record on the same domain or subdomain should have a unique priority value. Flowforth uses a priority of10 by default. If another MX record already uses 10, change the Flowforth record to a different value like 20 or 30.
Priority values range from
0 (highest priority) upward. If a priority value is already taken on the same subdomain, simply pick any unused number.If you need help resolving a conflict, contact support@flowforth.co.