Error: This domain has email enabled, but none of the MX records point to it.

13 posts / 0 new
Last post
#1 Wed, 10/22/2014 - 00:45
ADDISON74

Error: This domain has email enabled, but none of the MX records point to it.

When I am loading 'DNS Records' section I am getting the following error message with red color:

Warning - errors were found in this domain's DNS records : This domain has email enabled, but none of the MX records point to it. Either the MX records should be corrected, or the email feature disabled if mail is hosted externally.

Here is my BIND configuration:

$ttl 38400
mytestdomain.com. IN SOA mytestdomain.com. root.server1.mytestdomain.com. (
                        1413838061
                         10800
                        3600
                        604800
                        38400 )
mytestdomain.com. IN NS ns1.mytestdomain.com.
mytestdomain.com. IN NS ns2.mytestdomain.com.

mytestdomain.com.         IN A 188.215.36.123
ns1.mytestdomain.com. IN A 188.215.36.123
ns2.mytestdomain.com. IN A 188.215.36.123
www.mytestdomain.com. IN A 188.215.36.123
ftp.mytestdomain.com. IN A 188.215.36.123
mail.mytestdomain.como. IN A 188.215.36.123

mytestdomain.com.     IN MX 5 mail.mytestdomain.com.
mytestdomain.com.      IN TXT "v=spf1 a mx a:mytestdomain.com ip4:188.215.36.123 ?all"

As you can see mailmytestdomain.com has an IP address and also has a MX record.

I am hosting on a VPS with OpenVZ, I never got such of error message in KVM or VMware. I need and advice how to correct this issue.

Thank you.

Wed, 10/22/2014 - 10:05
andreychek

Howdy,

That error suggests you do have an MX record, but that it doesn't appear to be pointing to your server.

What output do you receive if you run this command -- this will show what IP addresses are active on your server:

/sbin/ifconfig

Wed, 10/22/2014 - 10:26
ADDISON74

Here you go:

lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:83 errors:0 dropped:0 overruns:0 frame:0 TX packets:83 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5780 (5.6 KiB) TX bytes:5780 (5.6 KiB)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:127.0.0.2 P-t-P:127.0.0.2 Bcast:0.0.0.0 Mask:255.255.255.255 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 RX packets:38973 errors:0 dropped:0 overruns:0 frame:0 TX packets:38530 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5209959 (4.9 MiB) TX bytes:14554113 (13.8 MiB)

venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:188.215.36.123 P-t-P:188.215.36.123 Bcast:188.215.36.123 Mask:255.255.255.255 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1

venet0:1 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:188.215.36.142 P-t-P:188.215.36.142 Bcast:188.215.36.142 Mask:255.255.255.255 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1

Wed, 10/22/2014 - 11:38
andreychek

Howdy,

Ah, it doesn't appear that the IP address listed in your DNS settings points to an active IP address on your server.

Are you certain that's your correct IP address?

If so, it's possible that it still needs to be setup on your system.

-Eric

Wed, 10/22/2014 - 11:43
ADDISON74

As you can see I got two IP's:

188.215.36.123 188.215.36.142 (this one is alias)

In my opinion BIND configuration is just fine. Any actions pointed?

Thu, 10/23/2014 - 11:33
ADDISON74

Solved. Two errors in this configuration created the problem Very strange because it was done by Virtualmin itself.

This is wrong mytestdomain.com. IN MX 5 mail.mytestdomain.com.

This is correct mail.mytestdomain.com. IN MX 5 mytestdomain.com.

Wed, 05/17/2017 - 05:48 (Reply to #6)
rx777

Thank you very much! But... how is it possible, that automatic configuration (as you said) makes such a wrong line of parameters?

Tue, 10/25/2016 - 08:11
apt_virtualmin

It is important to note that this error may also be triggered due to the following fully valid/not so rare situation.

  1. You are hosting mail for the domain on your server
  2. Your MX records point to a spam filtering smtp service that receives all that domains email directly filters it and then directs it to your local mail server
Wed, 06/07/2017 - 09:40 (Reply to #8)
jabowery

I am hosting mail for the domain on my server and I have enabled spam filtering by default in the creation of a virtual host. Does that explain why this error:

Warning - errors were found in this domain's DNS records : This domain has email enabled, but none of the MX records point to it. Either the MX records should be corrected, or the email feature disabled if mail is hosted externally.

crops up every time I create a virtual host?

As noted above, if I change:

mydomain.com. IN MX 5 mail.mydomain.com.

to:

mail.mydomain.com. IN MX 5 mydomain.com.

The error goes away.

Does this disable spam filtering as the cost of getting rid of the error?

If not, why is the error cropping up as the default for virtual server creation?

Thu, 10/12/2017 - 04:58
ADDISON74

It is not affecting spam filtering. I will report it as a bug.

Fri, 10/05/2018 - 14:47
thisara

I know this is a bit old thread. However I had the same issue and sorted out it correctly. What we need to have is a correct A record for the email.yourcoman.com as below before MX record. So it will look like below.

mail.yourdomain.com. IN A xxx.xxx.xxx.xxx
yourdomain.com. IN MX 5 mail.yourdomain.com.


The first poster's "ADDISON74" issue is, his A record is wrong.

mail.mytestdomain.como. IN A 188.215.36.123 <-- Notice the typo 'o' next to com
Should be,
mail.mytestdomain.com. IN A 188.215.36.123

Once this is corrected, I'm sure it will all work nicely. Good luck !

Mon, 10/08/2018 - 23:23 (Reply to #11)
Mon, 10/08/2018 - 23:29
andreychek

Thanks for your response thisara!

Freddy63, if you have questions or comments for thisara you may wish to ask those here :-)

-Eric

Topic locked