{"id":948,"date":"2021-07-23T12:41:53","date_gmt":"2021-07-23T12:41:53","guid":{"rendered":"https:\/\/ssdsunucum.com\/blog\/edit-mx-entry\/"},"modified":"2021-07-23T12:41:53","modified_gmt":"2021-07-23T12:41:53","slug":"edit-mx-entry","status":"publish","type":"post","link":"https:\/\/ssdsunucum.com\/blog\/edit-mx-entry\/","title":{"rendered":"Edit MX Entry"},"content":{"rendered":"<\/p>\n
\n
\n
\n

Valid for versions 82 through the latest version<\/em><\/p>\n<\/div>\n

\n

Version:<\/h4>\n

82<\/h4>\n<\/div><\/div>\n
\n

Overview<\/h2>\n
\n
Important:<\/div>\n
\n

We renamed<\/strong> this interface in cPanel & WHM version 96 and later to the Email Routing Configuration<\/em> interface (WHM >> Home >> DNS Functions >> Email Routing Configuration<\/em>).<\/p>\n<\/p><\/div>\n<\/div>\n

A mail exchanger (MX) entry determines which server receives mail for a domain name. The Edit MX Entry<\/em> interface allows you to configure the entry for each destination mail server.<\/p>\n

How to edit MX entries<\/h2>\n

To edit your server\u2019s MX entries, perform the following steps:<\/p>\n

    \n
  1. \n

    From the Choose a Domain to Edit<\/em> menu, select the name of the domain for which you wish to configure MX entries.<\/p>\n<\/li>\n

  2. \n

    Click Edit<\/em>. A new interface will appear.<\/p>\n<\/li>\n

  3. \n

    Select the Email Routing<\/em> setting that you wish to use. For more information, see the Email Routing table below.<\/p>\n<\/li>\n

  4. \n

    Enter the desired settings for each MX entry in the MX Entries<\/em> section.<\/p>\n<\/li>\n

  5. \n

    Click Save<\/em>.<\/p>\n<\/li>\n<\/ol>\n

    Email Routing<\/h3>\n

    You can select any of the following Email Routing<\/em> settings for your mail exchangers:<\/p>\n

      \n
    • \n

      Automatically Detect Configuration<\/em> \u2014 Select this setting to allow the system to choose the most appropriate Email Routing<\/em> setting, based on a query of the MX record. The system queries the MX record and uses the following criteria to determine the Email Routing<\/em> setting:<\/p>\n

        \n
      • \n

        If the lowest priority mail exchanger points to an IP address on this server, the system selects the Local Mail Exchanger<\/em> setting.<\/p>\n<\/li>\n

      • \n

        If a mail exchanger with a higher priority points to an IP address on this server, the system selects the Backup Mail Exchanger<\/em> setting.<\/p>\n<\/li>\n

      • \n

        If there are no mail exchangers that point to an IP address on this server, the system selects the Remote Mail Exchanger<\/em> setting. <\/p>\n

        \n
        Note:<\/div>\n
        \n The system cannot perform automatic detection for this setting if the MX entry does not resolve (for example, if you mistype a domain name or enter one that does not exist). If the MX entry does not resolve and the Email Routing<\/em> setting is Automatically Detect Configuration<\/em>, the system generates a warning and defaults to the last known Email Routing<\/em> setting.\n <\/div>\n<\/div>\n<\/li>\n<\/ul>\n<\/li>\n
      • \n

        Local Mail Exchanger<\/em> \u2014 Select this setting to cause the server to always accept mail for the domain.<\/p>\n<\/li>\n

      • \n

        Backup Mail Exchanger<\/em> \u2014 Select this setting to cause the server to accept mail for the domain and store it until a higher priority (lower number) mail server becomes available.<\/p>\n<\/li>\n

      • \n

        Remote Mail Exchanger<\/em> \u2014 Select this setting to cause the server to never<\/strong> accept mail for the domain. <\/p>\n

        \n
        Note:<\/div>\n
        \n

        The system always assigns the lowest priority value to Remote Mail Exchanger mail servers.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n<\/ul>\n

        \n
        Note:<\/div>\n
        \n

        For the Automatically Detect Configuration<\/em> setting to treat additional IP addresses as local, you must add them to the list of local IP addresses. Add IP addresses to the list in WHM\u2019s Configure Remote Service IPs<\/em> interface (WHM >> Home >> IP Functions >> Configure Remote Service IPs<\/em>).<\/p>\n<\/p><\/div>\n<\/div>\n

        MX Entries<\/h3>\n

        You can configure the following values for each MX entry:<\/p>\n

          \n
        • \n

          TTL<\/strong> \u2014 This integer value specifies the time to live (TTL). TTL indicates how long a particular record remains in memory, in seconds, before it refreshes. This value defaults to 14400.<\/p>\n<\/li>\n

        • \n

          Priority<\/strong> \u2014 This integer value represents the priority order of the mail server, in relation to other MX entries. The lower the Priority<\/em> value, the higher the server\u2019s priority. This value defaults to a value that is 10 higher than the highest existing MX entry\u2019s priority.<\/p>\n

            \n
          • \n

            The servers with the lowest Priority<\/em> values act as the primary mail servers.<\/p>\n<\/li>\n

          • \n

            Servers with higher Priority<\/em> values serve as secondary mail servers.<\/p>\n<\/li>\n

          • \n

            If multiple mail servers have the same Priority<\/em> value, the system distributes mail at that Priority<\/em> value to those servers randomly.<\/p>\n<\/li>\n<\/ul>\n<\/li>\n

          • \n

            MX Destination<\/strong> \u2014 Enter the name of the mail server (for example, \u2018mail.example.com\u2019).<\/p>\n<\/li>\n<\/ul>\n

            Add and delete MX entry text boxes<\/h3>\n

            To add a new MX entry text box, click Add Another MX Entry Field<\/em>. A new row will appear.<\/p>\n

            To delete a row, click Delete<\/em> next to that MX entry.<\/p>\n

            \n
            Note:<\/div>\n
            \n The bottom MX entry text box is always<\/strong> a new MX entry, and displays the label (new)<\/em> in the furthest right column.\n <\/div>\n<\/div><\/div>\n","protected":false},"excerpt":{"rendered":"

            Valid for versions 82 through the latest version Version: 82 Overview Important: We renamed this interface in cPanel & WHM version 96 and later to the Email Routing Configuration interface (WHM >> Home >> DNS Functions >> Email Routing Configuration). A mail exchanger (MX) entry determines which server receives mail for a domain name. The …<\/p>\n","protected":false},"author":1,"featured_media":949,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/948"}],"collection":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/comments?post=948"}],"version-history":[{"count":0,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/948\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media\/949"}],"wp:attachment":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media?parent=948"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/categories?post=948"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/tags?post=948"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}