Can I make two mx entries for one domain and two mail services?

Started by Popandopulos, Aug 25, 2022, 06:48 AM

Previous topic - Next topic

PopandopulosTopic starter

There is a task at the enterprise to make a corporate e-mail for all employees like
I would like to use a local free mail server, but there are long power outages (the oops is not enough) and sometimes the internet is unstable.
Therefore, there are a few boxes (director, marketing), which need 100% deliverability of emails.
I think these few boxes to the mail service google mail.
It will be expensive to put all mailboxes of my company (more than 50 pcs) there.
So the question, is it possible to have all mail boxes which are connected to domain, but that the part of boxes has been served by paid, but stable email hosting, and other part less important boxes served by a local email server of the enterprise?


I think in your case you need to do split delivery.
In brief:
gmail gets ALL the mail, it keeps all the mail it knows (existing mailboxes) and forwards all the mail that it doesn't know to your server.
Opportunity of this adjustment, however, can depend on a tariff plan on gmail.
Well and it is necessary to concern attentively to adjustment of mail DNS records to have an opportunity to send mail as with gmail and with self hosted.


An MX record is created for a mail domain, that is part of the address after the @. It does not allow you to divide servers by mailbox name.
You can only separate mails by domain, separately and separately
@ IN MX 10
mail IN MX 10


P.S. oh yes, i forgot the answer to your question.
You can have two (or more) MX records for one mails domain and different mailservices, but their purpose is totally different and you will not use them for your scheme.
There are services that allow you to host all the mailboxes of your organization on a reliable mail hosting service. The cost should please your accounting department.


It is impossible to forward the SMTP port on the NAT gateway to two different servers so that the gateway chooses where to forward mail depending on the recipient's domain: the gateway does not know anything about the SMTP protocol.
One of the options is to install a mail server on the gateway so that it routes mail, but whether and how easy it is to do this depends on the hardware or OS of the gateway.

It is better, in my opinion, to understand mail routing directly on the mail web server. In this regard, explain in more detail (otherwise I did not understand - the word "domain" has too many meanings): are you planning to create a new AD forest or use the old one?
The answer to this question depends on exactly how to make the transition from the old to the new server: the fact is that the mail server on SBS is most likely also Exchange, only an older version, and there can only be one Exchange organization in the forest.