Resolved Google Mail DNS won't validate unless MX priority is 1

[burnley]

Anyone else starting to get Support requests from customers saying Google mail DNS setting won't verify due to the high priority MX not being set as MX(1) ASPMX.L.GOOGLE.COM In the last week we've started to get a number of these. This never used to be an issue... Anyone got a contact at google they could ask whats going on here? Setting it manually on the command line is a real pita

 

[Benoit_HaiSoft]

Hi,
Yes, same thing here.
Here's Plesk answer :

« There is internal feature for implementation custom priorities for MX record for domain. We need to figure out of the demand and the popularity for further planning of feature delivery.
I have created corresponding request on UserVioce portal:

• Ability to add MX DNS record with a custom priority from Plesk GUI

You can vote for this feature and leave comments. They are also reviewed by our development team and can influence the feature implementation.»


So don't hesitate to vote, that will help to see this feature implemented !

 

[Benoit_HaiSoft]

With Plesk Obsidian 18.0.30, it is now possible to set an MX priority value to 1 from the Plesk interface.
Thank you Plesk for such a quick fix.

 

[lenala]

You can ignore this and leave at 0.