Facebook
Twitter
burnley
Regular Pleskian
User name: burnley
TITLE
Using Plesk DNS is impossible to configure G Suite
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
CentOS Linux 7.8.2003 (Core)
Plesk Obsidian Version 18.0.29 Update #2, last updated on Aug 26, 2020 11:10 PM
PROBLEM DESCRIPTION
Lately more and more clients using Google's G Suite require the following DNS MX record published in their zone, otherwise the G Suite setup can't proceed:
domain.com.au. 3600 IN MX 1 ASPMX.L.GOOGLE.COM.
Note the MX priority value, it *MUST* be 1 for the G Suite setup. I can't see why the Plesk Panel offers a restricted set of MX priority values, while at the same time the cli tool allows it no problem. The manual fix for this request is to run this on the affected Plesk server:
plesk bin dns -a domain.com.au -mx '' -mailexchanger ASPMX.L.GOOGLE.COM -priority 1
We've already had several customers who took their DNS somewhere else because they couldn't manage it themselves and it cost them money to delay the G Suite setup.
This is a major bug by omission, the lacking interface is increasingly causing financial losses and we can't afford to lose more customers..
STEPS TO REPRODUCE
Try to add from the Plesk panel an MX record with priority 1. Doesn't work, but works fine in CLI. Unacceptable in this day and age.
ACTUAL RESULT
The customer isn't able to use the Plesk panel DNS management page to complete the G Suite setup.
EXPECTED RESULT
The customer should be able to use the Plesk panel DNS management page to complete the G Suite setup.
ANY ADDITIONAL INFORMATION
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug
TITLE
Using Plesk DNS is impossible to configure G Suite
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
CentOS Linux 7.8.2003 (Core)
Plesk Obsidian Version 18.0.29 Update #2, last updated on Aug 26, 2020 11:10 PM
PROBLEM DESCRIPTION
Lately more and more clients using Google's G Suite require the following DNS MX record published in their zone, otherwise the G Suite setup can't proceed:
domain.com.au. 3600 IN MX 1 ASPMX.L.GOOGLE.COM.
Note the MX priority value, it *MUST* be 1 for the G Suite setup. I can't see why the Plesk Panel offers a restricted set of MX priority values, while at the same time the cli tool allows it no problem. The manual fix for this request is to run this on the affected Plesk server:
plesk bin dns -a domain.com.au -mx '' -mailexchanger ASPMX.L.GOOGLE.COM -priority 1
We've already had several customers who took their DNS somewhere else because they couldn't manage it themselves and it cost them money to delay the G Suite setup.
This is a major bug by omission, the lacking interface is increasingly causing financial losses and we can't afford to lose more customers..
STEPS TO REPRODUCE
Try to add from the Plesk panel an MX record with priority 1. Doesn't work, but works fine in CLI. Unacceptable in this day and age.
ACTUAL RESULT
The customer isn't able to use the Plesk panel DNS management page to complete the G Suite setup.
EXPECTED RESULT
The customer should be able to use the Plesk panel DNS management page to complete the G Suite setup.
ANY ADDITIONAL INFORMATION
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug
