Change where NS2.box points

I am so sorry for posting, but I can’t seem to find the answer on the forums.

I want to change the IP of NS2.BOX so that it points at a slave nameserver (instead of pointing to the same IP as ns1.box)

My registrar has proper glue setup (ns1.box.example.com pointed to 1.1.1.1) and (ns2.box.example.com pointed to 2.2.2.2)

In my box settings I added a CNAME record and an A record which point ns2.box.example.com to 2.2.2.2 however when I check the slave’s (2.2.2.2) zone records it shows that ns2.box.example.com is pointed to 1.1.1.1 and the Status Check of MIAB shows that ns1/ns1.box.example.com both point to 1.1.1.1

How can I get around this? Do I just need to add a different glue record (say ns3.box.example.com) and point it to 2.2.2.2 and let ns1/ns2.box bot point to 1.1.1.1?

Did you try adding it to the “Using a secondary nameserver” section?

This is a link from the setup guide: https://schiller.im/guide/setting-up-a-free-secondary-dns-for-mail-in-a-box/
Setup guide is here: https://mailinabox.email/guide.html#domain-name-nameservers

In fact I have looked at both of those guides before and yes the host name ns2.box.example.com is entered into secondary nameserver section.

The issue seems to be that MIAB is overriding the NS records for ns2.box locally to the box’s IP even though I want it pointed elsewhere.

You could try using ns3 or anything else.

Alright so I suppose I can use ns3 but here are my issues with that. (Besides the issue of the warning that ns1 and ns1 are on the same subnet because they point to the same place)

First off, I created a glue record with my registrar that has ns3.box.example.com point to 2.2.2.2 (my secondary “slave” DNS server). Now, I’ve noticed with DNS checking tools they complain if the glue records don’t match the DNS records on the box. The only way I can solve this is by creating an A record on my box that makes ns3.box.example.com point to 2.2.2.2 but unfortunately that points all IPv4 traffic to 2.2.2.2

Is there not a way to enter this in as an NS record instead of an A record? Can this be overridden in the config?

I’m running a secondary dns, but I haven’t done that via the glue records. The glue should point to your ns1, ns2 on the box. If you are using Gandi you can separately set your name servers. I have set those to be ns1 and ns6.gandi.net. ns6.gandi.net is added to the slave section in MIAB. This will authorise that server to pull the zone. (Which it does about every 12 hours or so)

My personal secondary DNS is one I run. It doesn’t have a hostname naturally (say like gandi might have ns6.gandi.net) so where do I create its hostname? Do I create a glue ns3 for it?

Also having both glue ns1 and ns2 point to the same IP nameserver checkers complain they’re on the subnet and subsequently the same unit.

Alright so it all comes down to this… The WebUI’s custom DNS doesn’t seem to edit changing the A address of ns2.box.example.com.

Would I be burned at the stake if I change the A address of ns2.box.reischnet.com in the zones file itself? Or should I just forget about consistent naming a just have ns2.reischnet.com?