• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Forwarded to devs Problem with DMARC and Migrate to another server

Azurel

Silver Pleskian
User name: Azurel

TITLE

Problem with DMARC and Migrate to another server

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

CentOS 7.8 + Obsidian 18.0.28#3, CentOS 8.2 + Obsidian 18.0.29#1

PROBLEM DESCRIPTION

On the old server (CentOS 7.8, Obsidian 18.0.28#3) was DMARC not enabled.
On the new server (CentOS 8.2, Obsidian 18.0.29#1) DMARC is enabled.

After migrate a subscription the DMARC is in DNS missing.

So its import data, but don't adapt settings of the new system.
How can I fix this for all new added subscriptions(domains)?

STEPS TO REPRODUCE

Migrate a subscription from server1 (DMARC=disabled) to server2 (DMARC=enabled)

ACTUAL RESULT

Missing DMARC DNS entries in migrated domains

EXPECTED RESULT

DMARC DNS entries in migrated domains

ANY ADDITIONAL INFORMATION



YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
According to applied business logic, a DNS zone on the target server after migration must be the same as a DNS zone on the source. So, if DMARK DNS entries were missed on the source, it intended to be missed on the target. Updating the subscription settings according to the target server-specific is a task far beyond the Plesk Migrator responsibility.

There are custom solutions on how to bulk enable DMARC on subscriptions, like this one:

# plesk db "SELECT name FROM domains\G" | grep name | awk '{print $2}' | while read i; do plesk bin dns -a $i -txt "v=DMARC1; p=none" -domain "_dmarc" ; done
 
Back
Top