Thank you team for the amazing work with MIAB. I have the primary domain setup and all is great.
I feel i am so close in setting up the secondary domain for the box.
One thing i have not done on DOMAIN2 is set the nameservers to BOX1 nameservers. The A record for DOMAIN2 has an active website so that will need to stay doing that.
I am getting few errors in the status checks and just wondering if i do need to set the NS?
Also on DOMAIN2 i can see smtp cname, imap cname, webmail cname and so on. Would it be smart to remove all those?
And one last point - Should the second domain have a working BOX(dot)DOMAIN2(dot)COM/MAIL ? at the moment it is not
I think … the only thing you need to do (to add a second domain) is the one thing you say you didn’t do.
Have a look in the instructions, but from memory you just set the nameserver records for the second domain, and then create an email user for the second domain - MIAB does everything necessary. Your domain2 DNS should have nothing but the nameserver records, if you’ve other records, that will confuse things.
For the www.domain2.com on another server … that domain really should point to your box (as a nameserver) and MIAB provides everything. For a “foreign” www.domain2.com server, you just create A and AAAA records for www.domain2.com using MIAB admin - System / Custom DNS.
(Be aware, MIAB doesn’t create everything until the new user logs-in, so don’t expect to see all their mailbox files etc until that stuff is needed.)
You need to make a choice here. Either allow the name servers that are already handling your second domain’s DNS continue to do so, or have MiaB handle DNS for the second domain.
What you choose will determine what you need to do.
Generally the simplest, but not necessarily the best option is to switch name servers to your MiaB. Most simple websites and domains have just an A record, an AAAA record and a CNAME record, so setting those up in MiaB’s Custom DNS section is pretty straightforward.
However in your case …
it sounds like you are using shared hosting with several other records set to make life “easier” for clueless people. So you really need to understand what you are doing. The specific CNAME records you mentioned are all for email use, and I presume that you’ll no longer be using your web hosts email, so yes, they all can be removed. But wait, if you are not going to use the web hosts name servers why bother? Just don’t carry them over to the Custom DNS page of your MiaB.
As I said you have a choice to make. The other choice is to use your web hosting’s DNS rather than MiaB for the second domain. If you do this, you’ll need to remove the existing CNAME’s you already mentioned, as well as the MX record, DKIM record, and TXT SPF and DMARC records. You’ll replace them with the values shown on the External DNS page of MiaB. Now be aware that MiaB has DNS entries for absolutely everything someone running a mail server might ever need and most don’t have a clue what they are, so you’ll need to sort through the entries they show and determine what you really need.
Now there are pros and cons of either choice. The con I like to focus on is that MiaB by design is a single point of failure if you use it’s DNS for a second domain. Even the first domain, really. To avoid this you absolutely need to set up Secondary DNS for your domains if you plan to use MiaB for DNS.