I am playing around with my first MIAB. I have 4 private domains that I want to have email accounts for at the end.
I started with one of the domains I don’t use at the moment and used the external dns feature to learn about the necessary entries. That worked fine.
Now I tried to setup the second unused domain. This time I tried out miab as primary name server. I have set the ip of miab as that primary nameserver at my registrar, but after ~2h I still could not ping the domain. So I tried something else. Instead of setting miab as primary nameserver I added a zone file with an A and a NS entry both pointing to my box.
Ping works now but miab tells me:
The nameservers set on this domain are incorrect. They are currently <ip>. Use your domain name registrar’s control panel to set the nameservers to ns1.mail.<my-first-domain>.com; ns2.mail.<my-first-domain>.com.
Is it really necessary to let the NS point to ns1.mail.<first-domain> for DNS to work? Wouldn’t it be enough if the nameserver points to the right ip where DNS listens on port 53?
Setting up ns1/ns2.mail… works (miab does not show the above message anymore), but i would prefer if those domains are not coupled. Because I would prefer to change that “main-domain” of the box to be another domain later on (to have that main domain as reverse dns entry)
Also, it does not help with all of the other DNS related red status messages in that second domain.
When i do
dig <second-domain> @localhost MX I don’t get the box as valid MX entry. So I guess miab has copied the entries from the (now main) nameservers that I have set at my registrar. So my plan can not work…
Is there any way to mix external DNS and using miab as primary nameserver on different domains?
Happy about everything that helps me understand…
Thanks and have a nice day