Proper multi-domain setup

Hi! So sorry for the newbie question. I’ve tried to follow other similar threads, but my situation isn’t quite the same.

  • Like others, also using DigitalOcean droplet for email - only ONE droplet.
  • I want this ONE droplet (single IP) to process email for multiple domains.
  • Using external DNS.
  • Websites reside on a number of different IPs for each of the domains.
  • All domains will have their webmail on the one droplet.

I can’t figure out the proper procedure to do this.

The first domain set up fine as part of the MIAB installation - no issues. It created the configuration, and the domain is properly mapped. Email flows fine. No issues.

I then created a, and the system automatically set up the configuration with SOME (not all that were created for default users and all. The other issue was that the alias mappings all pointed to, not! Furthermore, the MX for is - I absolutely do not want that!

I manually adjusted aliases, users, DNS. Email IS working and flowing properly. However, when I go to the system status checks page it complains that the the MX and MX not pointing to as it thinks it should. Annoying and ugly, even though I do have things working.

The users now look like this:

Email Address		Actions								Mailbox Size	admin (remove privilege) | set password | archive account	463 KB		set password | make admin | archive account			3 MB		set password | make admin | archive account			907 KB		set password | make admin | archive account			837 KB

And the aliases look like this:

	Alias			Forwards To	Permitted Senders (*) (*) (*) (*) (*) (*)

(*) Items can be deleted.

Like I mentioned, the system status checks complain for and

:heavy_multiplication_x: This domain’s DNS MX record is incorrect. It is currently set to ‘10’ but should be ‘10’. Mail will not be delivered to this box. It may take several hours for public DNS to update after a change. This problem may result from other issues listed here.

So, how does one properly set this up, or am I close and only need to make some final adjustments? It appears that I took a left turn from the get-go and drove on the sidewalk before nosediving into the river… Thanks! :slight_smile:

Your requirements make sense.

It’s technically fine for D2’s MX to be Heck, it’s probably more reliable – fewer DNS records to maintain. Why is it an issue for you?

Here’s the catch: your mail host needs its reverse DNS to be set up correctly. And, you only get one reverse record [*].

As long as D2’s reverse DNS claims that it’s actually D1, D2’s mail will get marked as spammy.

Nice job setting all that up though.

* technically, that’s one reverse record per IP address. So, sure, you could assign multiple IP addresses to your mail-in-a-box, and have it respond correctly to multiple domains. To me, though, that sounds like a hassle… It’s probably easier just to run two separate MiaB instances.

The issue is that it’s not cool to say that company D2’s email is handled by company D1. I agree with your comment about simplicity. Thanks, Bronson!

@starbock Do you think that the millions of domains using GSuite (old GoogleApps) for their private & business domains with MX records as

Blank or @     3600     MX     1     ASPMX.L.GOOGLE.COM
Blank or @     3600     MX     5     ALT1.ASPMX.L.GOOGLE.COM
Blank or @     3600     MX     5     ALT2.ASPMX.L.GOOGLE.COM
Blank or @     3600     MX     10     ALT3.ASPMX.L.GOOGLE.COM
Blank or @     3600     MX     10     ALT4.ASPMX.L.GOOGLE.COM

Are not cool, too?

Why not to use just a generic sub-domain for your BOX, something like cloud.box4.mail or or, to manage all your DNS records and email accounts for,,… and so on? … just an idea than may help you!

Hi, what I mean by not cool is, for example: MX preference = 10, mail exchanger =

Yes, a generic sub-domain was also Bronson’s thought for simplicity, which I agree with. Thanks!

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.