We’re still experimenting with MIAB and trying to make sure it will do what we want it to do. I have a separate thread on general mail settings.
We’re looking at the role of glue records and trying to get our head around what is actually needed.
We currently have a number of domains with easydns DOT com. Some of these domains are production domains that support quite busy webservers and a large number of services running different services. These are things we do NOT want to change around.
We have never used Glue records as all our DNS management is done by easydns DOT com and we’re very happy with what we pay them to do. We’ve been reading a lot about glue records and apart from the rather silly name (I’m sure there’s a good reason for it), it appears that a Glue Record simply delegates responsibility for a domain down to a sub-server. Fine, makes sense.
However, we do NOT want to move all of our DNS management out of easydns DOT com, we’d prefer to keep it running as we have redundancy and latency protection, also we’ve just renewed a load of domains
After reading and re-reading the MIAB setup guide, we think there is zero need to actually use Glue Records at all if (and only if) your external DNS is setup correctly. This means we need to set up the right MX records, the right A* records for the mail server, the right DNSSEC records as indicated in the External DNS page of the MIAB console admin. This means that we can ignore most of the errors on the system setup page that are connected to DNS management.
Have we read this correctly? If so then we need to take responsibility for the DNS configuration which is fine. We’re all grown ups here (well not sure I am).
Thanks for reading,