Applicable to:
- Plesk Onyx for Linux
Symptoms
-
The TXT records below are set in Plesk > Domains > example.com > DNS Settings:
CONFIG_TEXT: example.com. TXT v=spf1 +a +mx ip4:203.0.113.2 -all
CONFIG_TEXT: example.com. TXT MS=ms79539195
-
After performing the DNS synchronization via the Microsoft Azure DNS extension the TXT records with the same host are concatenated into one TXT record:
CONFIG_TEXT: example.com. TXT v=spf1 +a +mx ip4:203.0.113.2 -allMS=ms79539195
-
The MXtoolbox SPF checker utility shows the following result in the SPF Syntax Check field:
CONFIG_TEXT: "Invalid syntax found"
Cause
Product issue:
-
#EXTPLESK-1319 "The extension now correctly syncs TXT records that have the same hostname."
Fixed in:- Microsoft Azure DNS 1.1.0 07 April 2021
Resolution
Workaround
If update is not possible for some reason you may try the following
As a workaround, manually correct the concatenated TXT records on Azure DNS side, the result should be as below:
CONFIG_TEXT: example.com. TXT v=spf1 +a +mx ip4:203.0.113.2 -all
CONFIG_TEXT: example.com. TXT MS=ms79539195
Comments
5 comments
Any update on this item? The impact for MS=ms12345678 seems low, as this is primarily used for domain validation during M365 setup and can be removed when validation is finished. However for v=DKIM1 this is not the case. Every update a customer makes, will need manual intervention.
Hello Serge van Isterdael
I'll clarify this and let you know.
Serge van Isterdael
The exact ETA will be available later but I got a confirmation that fix for this bug is in a roadmap.
Any update?
Hello Daniele Scattolin,
The bug EXTPLESK-1319 was fixed in the Microsoft Azure DNS of the 1.1.0 version on 07.04.2021
Please sign in to leave a comment.