ArticlesArticles Most Popular ArticlesMost Popular Articles
RSS Feeds
DrillDown Icon Table of Contents
DrillDown Icon 2020 Official Holidays & Support Schedule
DrillDown Icon IMPORTANT: End of Life of SHA1 on Windows Server 2003
DrillDown Icon IMPORTANT: Supported Operating Systems
DrillDown Icon PLEASE READ: Our Update Server IPs Have Changed
DrillDown Icon Support
DrillDown Icon modusGate for Microsoft Azure
DrillDown Icon Deploying modusGate on Microsoft Azure MarketPlace
DrillDown Icon Get started with modusGate on Azure
DrillDown Icon Setting up a Route with the Route Wizard
DrillDown Icon Test your mail flow
DrillDown Icon Setting up a Static IP address
DrillDown Icon Changing your MX Records
DrillDown Icon modusCloud
DrillDown Icon Alleviating Spam – Best Practices
DrillDown Icon directQuarantine Technical Information
DrillDown Icon modusMail & modusGate Technical Information
DrillDown Icon Other Product Technical Information
DrillDown Icon Professional Services
DrillDown Icon Newsletters
  Email This ArticlePrint PreviewPrint Current Article/Category and All Sub-Articles/Categories
Changing your MX Records

Changing your MX records


Once your connection(s) are tested and working, the next step is to change your DNS records.

  • On the DNS Server, modify the MX (Mail Exchange) record so that your mail domain points to the modusGate server instead of the Exchange.
  • Create an A or Host record that maps the new modusGate MX to the Gater server's IP address.
  • Since the new MX records can take anywhere from 12 to 48 hours to propagate, only remove teh mail server's MX after modusGate's MX has been propagated. Do this to hide your mail server from public view: when spmmers see multipel MX's for the same domain, they often bypass the primary (modusGate's) and target the secondary (the mail server).

If you wish to check whether your MX record change has been propagated try using our Email Security Grader tool at and enter your domain name.

Modified 3/22/2016
Keywords: MX record change
Article ID: 1928