Hey ​@AndrewTX,

Just to rule out the obvious, the names and values records in Amazon match the records that Klaviyo provides, correct? If so, we can rule that out as the issue. Whenever I see an issue like this, I like to take a look at 3rd party sites like MXToolbox or DNSchecker.org, and entering the NS and TXT record details in there. That helps determine whether the issue is Klaviyo-specific, or if other parties are failing to recognize the records as well. 

Additionally, if setting up records using dynamic routing (NS records) doesn’t work, you might see success with static routing (CNAME records). Finally, if you’ve reached a dead end, and CNAME records aren’t being recognized either, I’d recommend reaching out to Amazon, and letting them know that records that are entered onto AWS aren’t propagating as expected. Let me know if I can answer any additional questions regarding this.

As it turned out, what finally fixed the issue was using to a ‘Static’ sending sub-domain setup and manually adding the CNAME records and the TXT record.  Important to note that the Klaviyo value in the TXT record MUST go before the SPF/include statement.

Makes no sense why Amazon wouldnt propagate the Dynamic/NS records - they were recognized in several countries like Italy and Mexico, but not at any reporting location in the US.

Sometimes a domain seems active but then disappears because the DNS records haven’t fully propagated. Give it up to 48 hours depending on your DNS provider. Also double-check that both the SPF and DKIM records are correctly entered without extra spaces or typos. If it still doesn’t stick after that, you might try removing and re-adding the domain in your settings.