Hi, I am hoping someone can help me out. I have looked through similar posts here on the forums but havent been able to see or implement a solution.
I am getting this error on a particular domain in virtualmin
"Warning - errors were found in this domain's DNS records : This domain has email enabled, but none of the MX records maill.tld.com point to it. Either the MX records should be corrected, or the email feature disabled if mail is hosted externally."
The only way in which I have been able to remove the error is by creating a new mx record and setting it as
Record name: mail.tld.com. priority: 5 Mail server hostname: tld.com
I am hosting the mail server on the same VPS. There are 2 ip's on the vps, both domain and A record for mail.tld.com point to the same ip
So I am not sure why it is giving me the error?
If anyone can point me int he right direction I would really appreciate it, thanks.
Did you get this error from the beginning, or did you do some configuration on the domain at the time it started showing up?
The usual procedure Virtualmin does for the zone is like so: Create A records "tld.com" and "www.tld.com" and some others, pointing to the VPS' IP.
When you turn on "Mail for domain", it additionally creates: "mail.tld.com A [ip]" and "tld.com MX 5 mail.tld.com".
If any of the latter two are missing or set incorrectly (i.e. mail delivery to your VPS won't work), it'll print the error you encountered. Those records don't delete themselves though. ;)
Hi Locutus thanks for helping out. It seems as though after about 24-48 hours the error has now gone away...i have no idea what is going on.
The error only popped up recently which is why i am confused. I am not sure if it as a result of me playing with something or the recent crash that our provider had.
The strange part is this. When i had the error and I setup the MX record incorrectly, Virtualmin gives me no errors.
When it was setup correctly it would then give me the error.
By incorrectly i mean if i setup the A record and then proceeded to create the MX record and set the record name as mail.foo.tld and the mail server hostname as foo.tld there would be no error, but the mail would not be setup correctly.
If i then reversed that mail would not work but no error? Strange as it is, its working now so cant complain.
FYI: I got the exact same error message without changing anything at all, it just seemed that bind got terminated and needed to be restarted - for some reason, the diagnostics don't seem to recognize that bind isn't currently running.
Even if the config is 100% correct, you may also see this if the DNS glue records haven't yet propagated - i.e. dig mail.TLD.com differs from dig mail.TLD.com @localhost (assuming you're running bind locally)
HTH