I followed the setup guide on Friday last week and have had issues with my DNS showing up on the System Status Checks page.
Conveniently, I am running Mail-in-a-Box on a DigitalOcean instance and using Gandi as my registrar.
After three days, I am still seeing these errors:
Nameserver glue records are incorrect. The ns1.box.MYDOMAIN.us and ns2.box.MYDOMAIN.us nameservers must be configured at your domain name registrar as having the IP address XXX.XXX.XXX.XXX. They currently report addresses of [Not Set]/[Not Set]. It may take several hours for public DNS to update after a change.
The nameservers set on this domain are incorrect. They are currently [Not Set]. Use your domain name registar’s control panel to set the nameservers to ns1.box.MYDOMAIN.us; ns2.box.MYDOMAIN.us.
There is also an obvious error regarding
box.MYDOMAIN.us not resolving to the correct IP.
tools/dns_update about once a day to see if that would change anything (it didn’t).
I have verified all of these settings in my Gandi control panel. The glue records point to the correct IP, and the domain is configured to use the aforementioned nameservers.
I’m going to try using DigitalOcean DNS and see how that works.
Can you verify from the command line a) on your box and b) on another machine that the DNS is actually set correctly? e.g.:
host -t ns MYDOMAIN.us
Thanks for getting back to me Josh.
I was halfway through external DNS configuration with DigitalOcean when I stumbled upon another guide that I decided was a better option for me. I may reconsider using Mail-in-a-Box as a DigitalOcean one-click install, but I would rather just roll my own solution from scratch with the amount of tinkering I have had to do on this installation already.
I’ll probably reference your featureset and Github repo for guidance, so thank you for that as well.
Colinsf, Can you provide some more details of what issues you ran into?
For future reference to other users, it helps to include the domain name when asking for help with DNS so that we can check for glue records or whatever.
I am not comfortable publishing my domain name on this discussion forum which is why I omitted it in the first place.
My biggest issue is that Mail-in-a-Box is designed to take over DNS for a domain. My next biggest issue was that DNSSEC was not supported by my registrar’s nameservers. I would have needed external DNS anyway, and that is not officially supported by the package (or so it states). These two issues required enough configuration on my part that I decided to seek another solution.