CloudFlare support?

The nameservers set on this domain are incorrect. They are currently; Use your domain name registrar’s control panel to set the nameservers to;

Yes, MiaB is configured to be its own name server. This solves the problem of dealing with correctly configuring DNS records because email has more records and even more record types than most DNS servers offer.

You will have this warning forever so long as you are using a different name server than MiaB.

You can configure the records yourself by navigating to the ‘External DNS’ page in the MiaB dashboard and configuring the records accordingly.

The way I and others deal with this is I have a domain that use exclusively for the sending server domain. This way, other domains that I don’t want to force MiaB to be the DNS server of can just enter the MiaB domain in the MX record plus a few other records and everything is good to go.

If you use this method, just be sure to review the project Setup guide to be sure you select a TLD that isn’t a bad one (.com is good).

Sounds all good, but what about the problem of the records already been set ? It doesn’t look like m i a b is actually recognizing that I put the name server records in my cloud flare ? I should also add Cloudflare is not my registrar

MiaB is only checking if MiaB is the name server for the domain. If MiaB is not the name server for the domain, it reports this as a problem, because that is how MiaB is configured. There is nothing technically wrong with not using MiaB as your name server.

It pretty clearly is in my OP attached are the ns records on CF.

So if so, why reported not being used?

How do i update the glu records on CF

I know it’s not your problem,. But i can’t seem to find how?

Aren’t glu and ns the same

MiaB is intended to be used as the name server. When this has not been configured, the dashboard warns you. For most users, this is an indication that something is not configured correctly.

A nameserver record is a part of a domain’s WHOIS record that is always in the form of a URL and tells other servers where to ask about the location of a DNS record.

Glue records are custom name server records for domains that use their own domain for the nameserver record.

The glue records are created at your registrar where you configure the record to point at the IP address of your name server. It looks like you are using GoDaddy, and they do not refer to glue records as glue records, but something else so you will need to search for it.

After configuring the glue records as described in the MiaB dashboard, enter the name server URL into the nameserver for your domain.

Amazing, didn’t know that, and never seen a doc on the internet indicating as such. Will give it a go when i am freed up. Thanks!

I actually did know that, I currently have my glu records pointing from godaddy to Cloudflare, so does this mean that I should point them to the url of the name server that miab is hosting?

If that’s the case then I should be good then, as I already have all my other domains that are listed over at Cloudflare containing the proper NS’s for all my other domains I will send and receive email.

This is good, I think I will be good to go! Thank’s for all your great help!

Oh, I noticed that there is an option to add more than two glu records. I am thinking it would cause problems for miab to have it’s own NS and glu’s pointing to another dns like CloudFlare, correct?

Oh, and I have yet to de firewall my server, what ports need to be open for this to work? Edit (looks like udp/tcp 53 only…)

I would like it accessible only by me if possible.

So… Minimal surface attack area of possible, and only what is needed for the dns to function.

Hostnames. SMH - I so hate GoDaddy

You do not have glue records. Glue records use your domain.

Glue records will be what MiaB is recommending:

You seem to be confusing glue records with nameserver records. The nameserver record is part of the domain WHOIS record:

$ whois
   Domain Name: HTTPBUILD.COM
   Registry Domain ID: 2356086242_DOMAIN_COM-VRSN
   Registrar WHOIS Server:
   Registrar URL:
   Updated Date: 2021-01-29T09:24:01Z
   Creation Date: 2019-01-27T21:23:11Z
   Registry Expiry Date: 2022-01-27T21:23:11Z
   Registrar:, LLC
   Registrar IANA ID: 146
   Registrar Abuse Contact Email:
   Registrar Abuse Contact Phone: 480-624-2505
   Domain Status: clientDeleteProhibited
   Domain Status: clientRenewProhibited
   Domain Status: clientTransferProhibited
   Domain Status: clientUpdateProhibited
   DNSSEC: unsigned

You can also see nameserver records using dig:

$ dig ns +short

MiaB is instructing you that the nameserver record does not have the glue record.

You should not be pointing your glue records to Cloudflare.

Your domain should really only have glue records if there is a DNS server being run on the domain FOR the domain.

GoDaddy regularly configures this incorrectly. They add “glue records” pointing to your name servers. Which is just wrong. Hence, another reason to hate GoDaddy.


All of them. MiaB has its own firewall.

MiaB is intended to be accessible by everyone on the world wide web, as that is a critical part of using email.

isn’t dovecot a mail transfer authority?
Wait don’t answer that, Not sure I want to go down that rabbit hole, I’ll just open all the ports

Dovecot performs many tasks, among them is message delivery agent (MDA). Postfix performs the task of message transfer agent (MTA).

1 Like

Ahh, I see, I guess I meant the start of authority (SOA)
Edit: stuff has to propagate, will comeback later…

Like so?

Nope. Those are your name servers. A ‘glue record’ is created when you are running a DNS server on the same domain, serving the same domain. Which is what MiaB does.

GoDaddy likes to list the name servers IP’s, no matter who is hosting them, as glue records.

Sorry for my confusion. Sigh, may i ask what record type this would specially fall under in this case?