Skip to main content
Answered

Domain authorisation not happening after change of host


I have been trying to get an answer to this via support chat without luck…

We are having an issue with the authentication status of our domain for emails. We had been authorised but recently moved our website and domain host to a different service. We added the Intercom DNS records to the new host a couple of weeks ago but the status of the domain in Intercom is still showing as unauthenticated.

The new host is Squarespace.


What else can we try doing to resolve this? It is impacting our deliverability due to junk/spam filters.

Thanks
 

Best answer by Jacob Cox

Hi @Simon T11 !

 

A common issue when setting up DNS records is the name that you use with your DNS provider. Every provider has different rules around how to set up the CNAME.

I would recommend lopping off the last half of the Host Name when setting this up. So if your workspace says the name is intercom_domainkey.myapp.com, you would only include intercom_domainkey as the Name.

Can you give that a go and see if that gets things working for you?

View original
Did this topic help you find an answer to your question?

4 replies

Jacob Cox
Intercom Team
Forum|alt.badge.img+5
  • Sr. Technical Support Engineer
  • 441 replies
  • Answer
  • October 22, 2023

Hi @Simon T11 !

 

A common issue when setting up DNS records is the name that you use with your DNS provider. Every provider has different rules around how to set up the CNAME.

I would recommend lopping off the last half of the Host Name when setting this up. So if your workspace says the name is intercom_domainkey.myapp.com, you would only include intercom_domainkey as the Name.

Can you give that a go and see if that gets things working for you?


  • Author
  • New Participant
  • 3 replies
  • October 23, 2023

Thanks Jacob. I have made the change and we’ll see what happens.

I assumed that the same change would apply to the second CNAME record required: i.e. outbound.intercom.mapofme.co becomes outbound.intercom


Nathan Sudds
Expert User ✨
Forum|alt.badge.img+5
  • Top Expert
  • 296 replies
  • October 24, 2023

@Simon T11 let us know how it goes!

 

I think @Jacob Cox has a good suggestion here, I've seen this with Godaddy as well... if there's still an issue maybe you can share a screenshot of the issue hopefully we can help you further. 


  • Author
  • New Participant
  • 3 replies
  • October 25, 2023

Hi Jacob and Nathan. Thanks for the tip. It worked.

For anyone else dealing with Squarespace as the DNS host this is what I had to configure for the CNAME record names:

intercom._domainkey (note: there is a full stop after intercom before the underscore. I assumed it was a mistake and removed it. It wasn’t until I added it back that it authenticated.)

outbound.intercom

Also I noticed that if you use the copy function from the Intercom page it adds a full stop to the end of both the Name and the Value text which need to be removed.

Thanks for your help.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings