Hi there,

We added a new domain as dedicated sending domain but it changed it on all our accounts. The most important thing now is to get the old sending domain back working with the account we have used for a year. If I add the domain back to that account will I then have to warm up the domain again?

I’ve been in contact with support but no answer for 36 hours and I really just need to know if I can do this to start sending straight away. What we have to do with the other account that should have another domain is for another time because it’s for a new market with no subscribers.. so really we just need to get it back as it was before.

Hi Patrick! Thank you for your comment. If the sending domain you are looking to use again has been dormant for more than a month, then yes, you would need to re-warm that sending domain. Also, I have a separate FAQ for this question here: 

Let me know if you have any further questions!

Hi All,

I have a number of Klaviyo accounts that have been set up for various international markets we operate in, yet the dedicated sending subdomain is the same in each instance (which I’ve read is totally fine)

Where I’m having trouble is getting our SPF records set up correctly, because one of the key rules of SPF is that you can only have one instance of each mechanism.  So multiple instances of klaviyo-site-verification=xxxxxx causes a permanent failure.

Does anyone have a work around for this?

Hey @Frankie22,

After setting up and having your dedicated sending domain verified and recognized, you can actually remove that record from your DNS. That specific klaviyo-site-verification=xxxxxx record is there to allow the verification process to take place. Once completed however, removing it would not cause any issues. 

David

I have 3 websites and 3 of them have klaviyo accounts.I need to add  sending domain for these . for that i add root domain as xyz.com in the 3 and create sending domain separate for 3 of them . Like promotion.ab,promotion.cd ,promotion.de,is there any issue to add like this?The @ usually means that it is set in the root domain, and currently each country domain is set in the xyz.com domain zone. Can I register a txt record to xyz.com?
If I choose to create a separate domain zone for each country domain, then face the following issues The existing country domains are registered with “shops.myshopify.com” as CNAME records, and CNAME records cannot be registered with other records in the same domain name. Also, route53, which is currently managing the domain, does not allow you to register information other than AWS as a CNAME record in the root domain. Therefore, we need to change the country domain to A record and register it based on IP.

Any possible suggestion?