Nameserver/DNS issues with MIAB box

Hi all, MAIB is fantastic/amazing!

Thanks to Josh and everyone else involved in community, etc.

I’ve set up MAIB successfully on a Linode box but am finding nameserver/DNS issues challenging! :confounded:

  • Box is [] at Linode
  • Glue record for domain set at registry
  • Setup secondary DNS at and

Intention is for the handle email and web for, and (low volume email/web).

When I run through a DNS check it throws up various issues including:

Recursive Queries I could use the nameservers listed below to performe recursive queries. It may be that I am wrong but the chances of that are low. You should not have nameservers that allow recursive queries as this will allow almost anyone to use your nameservers and can cause problems. Problem record(s) are:


When I repeat the DNS check with it throws up:

Missing nameservers reported by parent FAIL: The following nameservers are listed at your nameservers as nameservers for your domain, but are not listed at the parent nameservers (see RFC2181 5.4.1). You need to make sure that these nameservers are working.If they are not working ok, you may have problems!
Error Missing nameservers reported by your nameservers ERROR: One or more of the nameservers listed at the parent servers are not listed as NS records at your nameservers. The problem NS records are:
This is listed as an ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS records at the root servers and the NS records point to your own domain, for example).

Would really appreciate any feedback regarding:

(a) how I can address these issues, and

(b) if there is a better way of setting up DNS/nameservers.

One issue I’m not clear on is whether or not I should use (added to MAIB custom DNS) as primary nameserver for (+glue record), and

Context: is a primary business domain ( previously) and a personal domain.

Thank you! :slight_smile:


nameservers can take up to 48 hours to propagate at the registrar. Just give it some time :slight_smile:

Thanks Murgero, am aware of this but a good reminder! :wink:

1 Like

hey no problem, I checked your DNS and it’s still throwing an error, who is your registrar and did you name the nameservers “ns1.domain.tld” and “ns2.domain.tld”? You will need to make sure they are like that. Also make sure the right IP Address as well. I checked my MIAB instance and it is working as expected with similar setup to what you described.

Also - I would remove the record from the nameservers and use your DNS server’s in MIAB as your primary.

Registrar is

Nameservers are set to and (box name is resolves to which is correct.

the Linode MAIB box is primary NS for the domain as far as I can see.

Hmmm. is listed with the registrar as secondary NS with the MIAB box as primary.

I’m wondering why is allowing recursive lookups.

That would be the cause of the problem as the error is specifically stating it as the problem. I would check to see if you can remove that (Not needed as MIAB should be your complete DNS/NS server anyway)

Thanks Murgero for taking the time to reply again with more suggestions!

Linode is a pretty solid infrastructure player. I’d like to have as a backup nameserver should something happen to the MIAB box DNS.

I guess, if the DNS is down, it probably means the box is down, so … not much use.

Then again, if the internet can see that the box still lives (DNS still present) but the box is down, mail will be delayed but eventually delivered (assuming the box comes online within the applicable period within which the mail should be accepted - there will be an RFC for this somewhere I’m positive).

So on balance, secondary nameservers are worthwhile it seems, but I could have it wrong (if I have, please anyone, correct my ignorance!).



1 Like

In that case linode should be your primary nameserver and you should configure (see the admin web panel) MIAB as the secondary.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.