Transactional Emails / MX record

Develop, Build & Integrate CMS Development
1

Hello, We have purchased the Transactional Emails and are currently working with our IT department to set them up.
However, our IT team has some questions about the logic behind the MX record requirement. Specifically, they are unsure about the need for an MX record and, even more so, the requirement for it to be set to priority 0.

Below are the questions/concerns:

What is the logic behind the requirement for an MX record to implement the solution?
After all, the vast majority of these are primary domains of the organization that have an existing, complex, and critical mail traffic setup.
You probably understand that something like this will break our mail traffic on any domain where such a thing is done..
I don’t understand the requirement for an MX record, and even more so at priority 0, i would be happy to explain.
Maybe it is more customary and acceptable to register and manage a separate domain dedicated to this?

Thanks

2

Hi @Camille11,

According to this HubSpot knowledgebase article for connecting dedicated IPs, the MX record “processes bounces, spam reports, and unsubscribes to ensure the associated analytics will display in your HubSpot account after you send an email. The MX record priority must be set to 0 in your DNS hosting provider. Some DNS providers have a separate numeric field for Priority and you may have to enter the record value and numeric fields separately.”

As far as I know, the MX record should be issued on a subdomain (i.e. 246924h.yourwebsite.com) and not your primary domain (i.e. yourwebsite.com or www.yourwebsite.com). The MX record for the sudomain prevents any interference on the mail functinality associated with your primary domain.

Hope this helps!