Using MIAB for both DNS and mail. I have it set with the hostname mail/acme/com (replacing with acme here and using / because i cant do a posting with links)
My name registrar limits the glue records in the DNS settings to the main domain and not sub domains so I can only have glue records for ns1/acme/com and not ns1/mail/acme/com
I don’t think this is a major issue but as there would be many people running both dns and mail services under MIAB, is there a recommend way to set this up ? I could rename the MIAB to ns1/acme/com and then do an A record for mail/acme/com but then I would also have to go and set the conf file for the HELO postfix response to the be mail/acme/com s well
Is there something I’m missing ? I would have thought this is something straightforward that would be covered in the setup
This works because the dns server listens to the ip address, not the domain name.
It might be necessary to add mail.acme.com as a Secondary dns (under custom dns) but I’m not sure. Just try it without first.
I have a similar issue with my domain registrar (Hover). They require 2 DNS servers whose IPv4 addresses must be different. So, I have a VPS with 2 public static IPv4 addresses, and I have setup the 2 glue records:
Each points to one of the public static IPv4 addresses of my MiaB VPS. Then, I have set 2 DNS servers with my registrar:
ns1/mydomain/tld/
ns2/mydomain/tld/
Both IP addresses are configured and visible on my MiaB VPS (ip addr shows them both). However, MiaB’s DNS server only listens on one of the IPs. That means that clients who choose ns2/mydomain/tld as the nameserver to consult won’t find a DNS server running there, and will have to fallback to ns1.
Is there a way to tell MiaB’s DNS server to listen on both IPs?
An easy way to deal with this is to use a “secondary nameserver”. The secondary is normally somewhere completely different to your box - might be provided by your registrar or some third party - I used to use gandi but now use the free (and has been very reliable) puck.nether.net. The secondary maintains a copy of the records from your nameserver and is otherwise independent.
The settings are under admin / custom nameserver. Basically you specify your domain name and your nameserver IP address to the secondary, and then identify the secondary to MIAB to allow the secondary to copy your records.
You might need the “xfr” option on MIAB to permit the secondary to make a copy, the entry under admin / custom nameserver is something like “secondary.server.com xfr:123.123.123.123”.
Ok, then use that. Set ns1.acme.com as your dns server. Set glue records for ns1.acme.com. It should still work. There only needs to be a reference to the ip address, and this will do that.
