To direct your email traffic to LibraCyber ESG you need to update your domain’s “MX records”. The MX records are stored at your domain host and will direct your email to your mail servers. It’s like registering your new address with the post-Microsoft so that your mail gets delivered.
The MX record should be updated to point to your LibraCyber ESG appliance.
Modifying Your Domain’s Zone File (MX setup)
Every domain registrar has slightly different MX configuration procedures, but users can use these general steps as guidance.
- Sign in to your domain’s account at your domain host.
- Locate the page for updating your domain’s MX records. The page may be named something like “DNS Management”, “Name Server Management”, or “Advanced Settings”.
- Add new MX records for the ESG mail servers. The destination value is the public name of your ESG appliance. If you have a cluster setup, you need to add two records and choose a relative priority for the nodes: if you give the same priority to a node both will be used for incoming mail, otherwise, the node with higher priority (i.e. a bigger number) will be used, while the other node will be a fallback mailserver.
Example values for ESG MX records
| Name/Host/Alias | Time to Live (TTL) | Record Type | Priority | Value/Answer/Destination |
|---|---|---|---|---|
| @ or leave blank | 3600 | MX | 10 | esva1.example.com |
| @ or leave blank | 3600 | MX | 10 | esva2.example.com |
- Delete any existing MX records All other MX records should be deleted, as they are no longer used directly. If you can’t delete the existing MX records, just make sure that they have lower priority than your new ESG records.
- Save your changes.
NOTE: MX records changes require some time to take effect. Typically, after 1 to 6 hours you’ll start receiving your mail through ESG, but sometimes it may take up to 48-72 hours. Unfortunately, there is nothing that can be done to speed up this process, but there is also no drawback since in the meanwhile you’ll keep receiving to your mail server directly.