Resolving the Issue of Duplicate SPF Records for Your Domain

Why Multiple SPF Records Are a Problem?


A domain can have only one SPF record with the v=spf1 tag. If there are multiple SPF records, receiving email servers will not combine or interpret them correctly, leading to SPF permerrors.


Example of Duplicate SPF Records:

For the domain in question, there are currently two SPF records in the DNS:


v=spf1 include:amazonses.com ~all

And

v=spf1 include:_spf.vladimirharutyunyan_xyz._d.easydmarc.pro ~all



How to Resolve Duplicate SPF Records?


Option 1: Keep EasySPF Active

If you choose to use EasySPF for managing your SPF:


Retain the EasySPF record:


v=spf1 include:_spf.vladimirharutyunyan_xyz._d.easydmarc.pro ~all


  

Add sending sources (e.g., Amazon SES) inside EasySPF via the EasyDMARC dashboard. This eliminates the need for additional SPF records in your DNS and helps ensure your configuration stays within the 10-DNS lookup limit.


Note: You can include both the EasySPF statement and the include statement for a sending source within a single SPF record. However, it’s crucial to stay within the 10-DNS lookup limit and ensure the source is either added to the DNS SPF record or managed through EasySPF to avoid duplication!


Option 2: Manage SPF Manually:


If you prefer to manage SPF directly in your DNS, you’ll need to consolidate all sending sources into a single SPF record.


Example of a Consolidated SPF Record:


v=spf1 include:amazonses.com include:_spf.google.com ~all  



Important: If managing SPF manually, remove the EasySPF include statement (include:_spf.vladimirharutyunyan_xyz._d.easydmarc.pro) to avoid duplication.


How EasySPF Helps?


If you decide to use EasySPF for your SPF management:


It consolidates all your sending sources into one SPF record, keeping your configuration within the 10-DNS lookup limit.


It eliminates the hassle of managing SPF records manually in your DNS.

If you prefer manual management, be sure to update your DNS with a single, consolidated SPF record and regularly monitor it as you add new sending services.


For more information and configuration please check this article