I’m seeing this problem with all domains that don’t use the miab dns; the domains are using my private nameservers on my shared hosting at HostGator. I changed the domain name and IP address in the example below. Other than that, the text is verbatim. I only have one mx entry per domain, and it’s 10 at my miab.
The nameservers set on this domain are incorrect. They are currently [Not Set]. Use your domain name registrar’s control panel to set the nameservers to ns1.box.miabdomain.tld; ns2.box.miabdomain.tld.
This domain’s DNS MX record is not set. It should be ‘10 box.box.miabdomain.tld’. 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.
This domain should resolve to your box’s IP address (A 000.000.000.000) if you would like the box to serve webmail or a website on this domain. The domain currently resolves to [Not Set] in public DNS. It may take several hours for public DNS to update after a change. This problem may result from other issues listed here.
The mail appears to work on the domains with this status. I’ve only recently started migrating the mail from these domains to miab, so I’m unsure about these messages. Is this a bug in the system?