Each sub-domain may have a specific email service provider designated to it using DNS MX records, however the domain portion of the email address is what determines the MX records that are read and therefore the mail server which receives the inbound emails.
For the solution you have requested where different mail service providers are used concurrently for a single domain a more complicated setup is required, and to be honest its not a great solution. This is a problem I come across all the time, particularly with small businesses and charities who may have a large number of users who are happy with a standard web-mail interface and SMTP/IMAP to send/receive emails from their desktops and mobile devices, but perhaps only a handful of users that need a full exchange setup with shared folders, shared calendars, task management, global contact lists and Active-Sync push mail to their mobile devices etc. Unfortunately the mail server configuration cannot be configured per email address and must always be a per-domain configuration.
I have included 3 options here for how you could proceed, mainly to ensure you're aware of them all and have considered them, but in terms of answering your question where you have specified you would like to concurrently use a selection of email providers and from a single domain name, and do not wish to consolidate to a single email provider for all your email users, your only realistic option for moving forward is likely to be Option C below.
Option A: Email Provider Consolidation
You all choose to standardise on the email platform you will use on that domain name - for example all of you use Google Apps or all of you use Office 365 or all of you use another provider. This is the only solution which will enable you to both send and receive email with the branding of the primary parent domain (
Option B: Domain Name Separation (using different gTLD's)
If there are only a couple of mail providers to use concurrently then sometimes companies have managed this split by using an
@example.com domain for one provider and an
@example.org for the other provider. By using a different domain name for each email provider there is no longer a routing problem, and to avoid any lost messages from confusion or guessed email addresses, you could setup email aliases/forwarders at each domain to ensure all messages reach their intended mailbox users. For example:
Email Provider 1 (example.com): firstname.lastname@example.org --> email@example.com
Email Provider 2 (example.net): firstname.lastname@example.org --> email@example.com
Option C: Mail Forwarding at Parent Domain
- You configure the different MX records for each of the sub-domains as preferred by each mailbox user, and create mailboxes at each respective email service provider. To give an example, for
firstname.lastname@example.org you would configure the following MX records:
joe.example.com IN MX preference:10 exchange:aspmx.l.google.com
joe.example.com IN MX preference:20 exchange:alt1.aspmx.l.google.com
joe.example.com IN MX preference:30 exchange:alt2.aspmx.l.google.com
joe.example.com IN MX preference:40 exchange:aspmx2.googlemail.com
joe.example.com IN MX preference:50 exchange:aspmx3.googlemail.com
- And then at the parent domain, point the MX and A records to mail servers for which there is a control panel you can access to configure email forwarding (substituting your server IP addresses for my made up ones):
example.com IN MX preference:10 exchange:mx1.example.com
example.com IN MX preference:20 exchange:mx2.example.com
mx1.example.com IN A 111.222.333.444
mx2.example.com IN A 111.222.333.444
- From there you can create an email alias/forwarder to redirect:
email@example.com --> firstname.lastname@example.org
email@example.com --> firstname.lastname@example.org
This will automatically route Joe's inbound email to Google Apps for him, however when he responds to his messages they will appear to come from
and then setup a Mail forwarder/alias to redirect inbound emails received at
To help with managing this, if you're not keen on seeing repetition in your email addresses perhaps you would choose your sub-domain names based on the email provider, for example:
email@example.com, or if you like shorter versions how about
If users are sending/receiving their email from Microsoft Outlook desktop software then you could configure the software to use the Google Apps IMAP server for receiving messages but to use the SMTP server of your parent domain for sending messages and then they would appear to be sent by
The same method can be used from mobile devices, but as far as I'm aware it is not possible if you are logging into the Google Apps web-based system or outlook.com or Office 365.