AWS Builder Center is the official home for builders on AWS. Share and read what others are working on, follow people who inspire you, explore training and workshops, and find tools to support what you're building.
TXT record not verifying with Klaviyo (third party) integration
Hello, I'm trying to set up a subdomain for email sending from Klaviyo, a third party marketing service. I've added the necessary records to my hosted zone, but the TXT record that is required is not verifying for some reason. I've ensured it's the exact same string and everything matches. Any ideas what may be going on? 
- Newest
- Most votes
- Most comments
When dealing with TXT record verification issues for third-party integrations like Klaviyo, there are a few things to consider:
-
DNS Propagation: DNS changes can take up to 48-72 hours to fully propagate across the internet. If you've recently added the TXT record, it might not be visible to Klaviyo's verification system yet. Wait for at least 24-48 hours before trying to verify again.
-
Record Format: Ensure that the TXT record is formatted correctly. Some DNS providers require that you enter the value without quotation marks, while others may require them. Double-check Klaviyo's documentation for the exact format they expect.
-
Subdomain vs. Root Domain: Make sure you're adding the TXT record to the correct domain or subdomain. If Klaviyo is expecting the record on a subdomain, ensure it's added there and not on the root domain.
-
Multiple TXT Records: If there are multiple TXT records for the same domain/subdomain, some DNS systems might only return the first one. Ensure the Klaviyo TXT record is the only one or the first one for that specific domain/subdomain.
-
Special Characters: If the TXT record contains any special characters, make sure they're properly escaped or encoded according to your DNS provider's requirements.
-
Record Name: Verify that the record name (also known as the host or hostname) is correct. It should match exactly what Klaviyo specifies.
-
TTL (Time to Live): While this shouldn't affect verification, setting a lower TTL (like 300 seconds) can help changes propagate faster for future updates.
If you've checked all these points and are still having issues, you may want to use a DNS lookup tool to verify that the TXT record is visible and correct from external sources. If the record appears correct externally but Klaviyo still can't verify it, you may need to contact Klaviyo's support for further assistance.
Remember, patience is key when dealing with DNS changes. If everything looks correct on your end, giving it more time to propagate might be the solution.
Sources
Amazon SES domain verification TXT records - Amazon Simple Email Service
Verifying a domain with Amazon SES - Amazon Simple Email Service
Troubleshooting DKIM problems in Amazon SES - Amazon Simple Email Service
