Even if you think you are sure you set up the information correctly, we suggest that you follow the troubleshooting steps below, just in case.
DKIM record is not approved
If the DKIM record fails:
Update the CNAME record Name to
litesrv._domainkey. In most cases, adding the domain at the end of the Name field text is not necessary, as it's done by the DNS providers automatically.Some DNS providers add the domain to the end of the Value field text by default. To avoid this, add your text with a period at the end
litesrv._domainkey.mlsend.com..Check if the record you’ve added matches the one provided in MailerLite exactly. If you’re unsure, you can compare both texts here.
SPF record is not approved
Your SPF record might not be approved for one of three reasons:
SPF records don't match
SPF Name record field must be left empty
Multiple SPF records found
1. Mismatched SPF records:
Ensure the SPF record in your domain's DNS settings matches exactly with the one on your MailerLite Domains page. This comparison is crucial because SPF records are case-sensitive. Any discrepancy, and your record won't be approved. Use a text comparison tool to check for exact matches. If your SPF record includes incorrect prefixes like 'Record:', remove them to ensure proper formatting.
2. SPF record Name/Host field should be blank:
In some cases, your hosting provider might not allow using your domain as the 'Name' or 'Host' field in any record. Instead, use '@' in the 'Name' or 'Host' field of the TXT record or simply leave it blank. However, if other records on your DNS page use a common 'Name' or 'Host' field, consider using that same field for your SPF record.
3. Multiple SPF records found:
You can only have one SPF record in your DNS zone. If there are multiple SPF records, they need to be combined into a single record:
Identifying multiple records: In your DNS settings, if you find more than one TXT record for SPF, these records must be merged.
Automatic merging by MailerLite: When you click the green "Check DNS records" button in MailerLite, the site will automatically check and update the SPF record's Value with the merged version.
Initial SPF Value: Initially, your SPF value might look something like
v=spf1 a mx include:_spf.mlsend.com ?all.Verification of Merge: Check the new SPF value. A successful merge typically includes more than one 'include' statement, like
v=spf1 a mx include:_spf.mlsend.com include:spf.protection.outlook.com -all.
Before adding the new merged SPF record:
Replace existing SPF record(s) with the single, merged record: Create a new TXT record with the merged SPF value. Afterward, be sure to delete all current SPF records in your DNS zone, including the unmerged MailerLite record.
Recheck with MailerLite: Go back to your MailerLite Domains page and click the "Check DNS records" button again.
An error may still come up, even after setting up the merged SPF record in the DNS zone. Don’t worry if this happens. Remember that servers can take up to 48 hours to completely update this information. Most of the time, however, it’s approved within a few minutes to a few hours. MailerLite will automatically recognize and approve the record once propagation is complete.
You can check if the SPF record is correctly set up with this third-party tool.
Note: If the method above is not working for you, take a look at our article How to merge SPF records.
Domain verification record is not approved
If the Domain verification record fails:
Make sure the Value of the record is added in full. Double-check that the Value you’ve added is not shorter than the one provided in MailerLite.
Similarly to the SPF record, the verification record requires the Name to be your root domain. Depending on your domain provider, leave the field blank, enter
@, or type in the domain name.
Note: If you've confirmed that your records are added correctly, they may just need more time to propagate. Usually propagation is completed in 24 hours, though in some cases it can last up to 72 hours.
You can check your propagation progress by using a DNS checker.