2

I checked my domain name with GSuite's MX tool to find out why our email gets to Spam folders, and have resolved the main issues (SPF and DKIM entries were missing in our DNS settings). The last problem is this:

"There should not be a mail exchanger set up on naked domain name"

enter image description here

Previously there was an A entry pointing to mail server of our hosting in DNS settings and I have removed it (since we use Google's mail servers anyways).

A few hours have passed, so maybe I just need to wait a bit longer, or should I do something else besides this?

c0dehunter
  • 271
  • 4
  • 11

2 Answers2

6

This warning is not about your DNS records, it's about your server: The server to which the DNS address records for example.com refers. They are saying that that server is running a mail server that answered port 25. There should be no mail server receiving mail on that server.

Michael Hampton
  • 237,123
  • 42
  • 477
  • 940
  • But since this is a shared hosting plan, I don't think our hosting provider will turn off the mail server, since some other users surely uses it. I guess this situation happens a lot because most of the people I know also use shared hosting plans and then use Gmail (GSuite) to acces their mail. Should I just ignore the error? – c0dehunter Dec 08 '18 at 20:02
  • If your website is on shared hosting, then there's nothing you can do about it except to move elsewhere. You'll have to ignore the error and hope you never lose mail. – Michael Hampton Dec 08 '18 at 20:20
0

Previously there was an A entry pointing to mail server of our hosting in DNS settings and I have removed it (since we use Google's mail servers anyways).

The fact that you use G Suite for your email doesn't negate the need for MX records. The G Suite documentation lists the MX records you should create in your DNS zone.

https://support.google.com/a/answer/174125?hl=en

joeqwerty
  • 108,377
  • 6
  • 80
  • 171