I’m trying to use miab as nameserver for a .de domain. my domain host gave me the following answer after I failed to publish the nameserver (mias server) entries for my domain:
The Nameservers are not configured correctly for your .DE name(s), that is why we are failing to publish them.
To test if a Nameserver is configured correctly for your .DE name you can use this tool: nast(dot)denic(dot)de
Please note that the IP addresses of each Nameserver should differ by at least one number in any octet and at least one of them must be connected via IPv4.
Who is you registrar. Does it really require 2 NS servers on separate IPs. I doubt it. Just enter ns1 and ns2 in your dashboard and you will be good to go. It will complain that the 2 ns servers are on same subnet but who cares. You need 2 NS records ns1.box.domain.dens2.box.domain.de and 2 A records ns1.box and ns2.box at the registrar. Most of the users here have such setups.
I’m running my miab for several years using .i.ng domains and didn’t ran into that issue. I recently decided to let the miab also handle my .de domains and I was not able to set the name servers to point to my miab instance until I added a third name server with a different ip yesterday. It seems that denic is very restrictive when it comes to the name server setup. They have a website for a NAST Predelegation Check: https://nast.denic.de/.
As long as you seen any errors you won’t be able to set the nameservers.