It's been 24 hours since I added an MX record
The name was @
, type was MX
and value was mail.heeldiaries.com
There's also an A
record with mail.heeldiaries.com
pointing to the IP of the server.
When I do a mail-tester.com test it is saying
We didn't find a mail server (MX Record) behind your domain name heeldiaries.com
We check if there is a mail server (MX Record) behind your domain name heeldiaries.com.
You may want to publish a DNS record (MX type) for the domain name heeldiaries.com or use a different bounce email address.
Have I setup this up wrongly or is there another problem?
Best Answer
You have much bigger problems in play here. When I attempted to run a
dig +trace +additional
on your domain, this is what I saw at the tail end of the output:ns1.heeldiaries.com
. While it's clear that glue exists for this DNS entry, there is a problem obtaining it from your DNS server.Next, let's check for the presence of
SOA
andNS
records. This should tell us whether the zone lives on the server at all, and whether we have some form of glue record mismatch.There is a glue record mismatch here. You have configured your registrar to return
NS
records of ns1 and ns2.heeldiaries.com, but the authoritativeNS
records living on your DNS server are returning those localhost.ltd entries instead. Considering that localhost.ltd is a bogus domain that doesn't exist, the fact that things are broken should not surprise anyone.Further, even if we ignore the fact that your domain completely breaks when the
NS
records are refreshed, you don't haveA
records defined for the nameservers in your glue:In short, your entire DNS configuration is hosed. If you were not the one who set this up, please have some stern words with the person who did. I strongly encourage you to move this domain to any number of free and reputable DNS hosting companies. You would not have had these problems if your company wasn't trying to host its own DNS with neither the appropriate resources (geo-redundancy) or training.