IceWarp MX Records: Setup Guide for Cloud and On-Premise Deployments
How to configure MX records for IceWarp email, covering both cloud-hosted and on-premise deployments with step-by-step DNS instructions.
IceWarp is an enterprise email and collaboration platform used by organizations that want a full-featured alternative to Microsoft 365 or Google Workspace. It offers email, calendaring, chat, document collaboration, and video conferencing, either hosted in IceWarp's cloud or installed on your own servers.
Setting up MX records for IceWarp depends on which deployment model you use. Cloud-hosted customers point MX records to IceWarp's servers. On-premise customers point MX records to their own mail server. This guide covers both scenarios.
Cloud vs. On-Premise: Which MX Records Do You Need?
The first thing to determine is how your IceWarp installation is deployed, because the MX record values are different for each model.
IceWarp Cloud (hosted by IceWarp). Your email is hosted on IceWarp's infrastructure. IceWarp provides the MX record values, and they manage the mail servers. This is the simpler setup.
IceWarp On-Premise (self-hosted). You have installed IceWarp on your own server. Your MX records need to point to your server's public IP address or hostname. You are responsible for the server's availability and configuration.
IceWarp Partner/Reseller hosting. Some organizations use IceWarp through a reseller or managed service provider. In this case, the reseller provides the MX record values, which may differ from IceWarp's standard cloud hostnames.
If you are not sure which model your organization uses, check with whoever set up IceWarp or look at your IceWarp admin console URL. Cloud customers typically access the admin at a subdomain of icewarp.com or easymail.icewarp.com, while on-premise installations use your own server's hostname.
IceWarp Cloud MX Records
For IceWarp Cloud deployments, the MX records point to IceWarp's hosted mail servers. IceWarp provides the specific values during your account setup, and they are available in your IceWarp Cloud admin console.
The typical MX records for IceWarp Cloud follow this pattern:
| Priority | Mail Server |
|---|---|
| 10 | mx1.icewarp.com |
| 20 | mx2.icewarp.com |
Confirm your specific values with IceWarp
IceWarp may assign different MX hostnames depending on your region or service tier. Always confirm the exact values in your IceWarp admin console or welcome documentation rather than relying solely on general guides. The values above are representative of a standard configuration.
The two records provide redundancy. The priority 10 server handles email normally, and the priority 20 server takes over if the primary is unavailable.
IceWarp On-Premise MX Records
For on-premise deployments, your MX records point to your own server. The values depend on your specific infrastructure:
| Priority | Mail Server |
|---|---|
| 10 | mail.yourdomain.com |
Replace mail.yourdomain.com with the actual hostname of your IceWarp server. This hostname must:
- Resolve to your server's public IP address (you need an A record for it)
- Have port 25 accessible from the internet (for SMTP mail delivery)
- Have a valid SSL/TLS certificate (recommended for secure connections)
If you have a backup or secondary mail server, add a second MX record with a higher priority number (e.g., priority 20) pointing to that backup server.
Important: The MX record should point to a hostname (like mail.yourdomain.com), not directly to an IP address. While some DNS providers allow MX records pointing to IP addresses, this violates RFC standards and can cause delivery issues with some mail servers.
Step-by-Step Setup for IceWarp Cloud
Step 1: Get Your MX Record Values
Log into your IceWarp Cloud admin console or refer to your welcome email. Find the DNS configuration section, which lists the MX records and other DNS records you need to add. Copy these values exactly.
Step 2: Log Into Your DNS Provider
Go to your domain registrar or DNS provider (GoDaddy, Cloudflare, Namecheap, or wherever your domain's DNS is managed). Navigate to the DNS management section for your domain.
Step 3: Remove Existing MX Records
Delete any MX records currently configured for your domain. Old records from a previous email provider will conflict with IceWarp's servers and cause unpredictable email delivery.
Step 4: Add IceWarp MX Records
Add each MX record that IceWarp provided:
- Host/Name:
@(represents your root domain) - Type: MX
- Value/Mail Server: The IceWarp mail server hostname
- Priority: The priority number IceWarp specified
- TTL: Leave at default (3600 is standard)
Save each record.
Step 5: Add Domain Verification Record
IceWarp Cloud typically requires domain verification via a TXT record. This proves you own the domain. Add the TXT record exactly as shown in your IceWarp admin console.
Step 6: Verify and Test
Wait for DNS propagation (typically one to four hours), then verify your records at mxrecordchecker.com. You should see the IceWarp mail server hostnames with the correct priorities.
Send a test email from an external account to your IceWarp mailbox. If it arrives, the setup is complete.
Step-by-Step Setup for IceWarp On-Premise
Step 1: Confirm Your Server Is Ready
Before adding MX records, make sure your IceWarp server is fully operational:
- The server is running and accessible from the internet
- Port 25 (SMTP) is open and not blocked by your firewall or hosting provider
- You have a hostname for the server (e.g., mail.yourdomain.com) with an A record pointing to the server's public IP
- IceWarp is configured to accept email for your domain
Step 2: Create an A Record for Your Mail Server
If you do not already have one, add an A record for your mail server's hostname:
- Host/Name:
mail(this creates mail.yourdomain.com) - Type: A
- Value: Your server's public IP address
- TTL: 3600
Step 3: Add MX Records
Now add the MX record pointing to your server:
- Host/Name:
@ - Type: MX
- Value/Mail Server:
mail.yourdomain.com - Priority:
10 - TTL: 3600
If you have a secondary mail server for redundancy, add a second MX record with priority 20 pointing to that server.
Step 4: Configure Reverse DNS
For on-premise deployments, configure a PTR (reverse DNS) record for your server's IP address. This maps your IP back to your mail server's hostname. Many receiving mail servers check reverse DNS and may reject or flag email from servers without it. Contact your hosting provider to set this up, as PTR records are managed by whoever owns the IP address block.
Step 5: Verify and Test
Check your MX records at mxrecordchecker.com. You should see your mail server hostname with the correct priority. Then send a test email from an external account to confirm delivery.
Email Authentication Records
Regardless of whether you use IceWarp Cloud or on-premise, you need email authentication records for reliable delivery:
SPF record: Authorizes your mail server to send email from your domain. For cloud deployments, IceWarp provides the SPF include value. For on-premise, you will include your server's IP address. Example: v=spf1 include:icewarp.com ~all (cloud) or v=spf1 ip4:YOUR.SERVER.IP ~all (on-premise). Verify at spfrecordcheck.com.
DKIM record: IceWarp supports DKIM signing. Generate the DKIM key in your IceWarp admin console and add the corresponding DNS record. Verify at dkimtest.com.
DMARC record: Defines authentication policy for your domain. Add a TXT record at _dmarc.yourdomain.com. A good starting point: v=DMARC1; p=quarantine; rua=mailto:[email protected]. Verify at dmarcrecordchecker.com.
Set up authentication after confirming MX records work
Get email flowing first with MX records, then add SPF, DKIM, and DMARC one at a time. This makes troubleshooting much easier if something goes wrong.
Common Issues and Troubleshooting
Email bouncing with "connection refused." For on-premise setups, port 25 may be blocked by your hosting provider or firewall. Many cloud hosting providers (AWS, Azure, Google Cloud) block outbound port 25 by default and require you to request an exception. Check with your hosting provider.
Email arriving but with delays. If your MX record points to a hostname that is slow to resolve, or your server is geographically distant from senders, delivery may be slower. Ensure your mail server hostname resolves quickly and your server has adequate resources.
IceWarp Cloud admin says domain is not verified. The TXT verification record may not have propagated yet. Wait an hour and refresh the admin console. Confirm the record was added at the correct DNS provider.
Receiving "SPF fail" on outgoing email. Your SPF record does not include IceWarp's servers (for cloud) or your server's IP (for on-premise). Update the SPF record and verify at spfrecordcheck.com.
On-premise: email rejected by recipients. Missing reverse DNS (PTR record) is a common cause. Many mail servers reject email from IP addresses without valid reverse DNS. Contact your hosting provider to configure the PTR record.
MX records correct but no email arriving. For on-premise deployments, verify that IceWarp is configured to accept email for the domain. In the IceWarp admin console, check that the domain is listed and has active mailboxes. For cloud deployments, confirm your account is active and the domain setup is complete.
Migrating to IceWarp From Another Provider
When switching from Google Workspace, Microsoft 365, or another provider to IceWarp:
Before the switch. Set up IceWarp fully: create all mailboxes, configure settings, and verify domain ownership. Lower your current MX record TTL to 300 seconds at least 24 hours before migration. IceWarp offers migration tools to import existing email from your old provider.
During the switch. Remove old MX records and add the IceWarp records. Verify the change at mxrecordchecker.com.
After the switch. Keep access to your old provider for a few days to catch stragglers. Monitor both systems during the propagation period. Once confirmed, raise TTL back to 3600 seconds.