Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,467,716
Community Members
 
Community Events
177
Community Groups

Changing DKIM selector for DKIM1 record - statuspage

Hi,

 

I am trying to configure DKIM on statuspage.

I am already using m1._domainkey on my DNS.

Is there a way to choose the selector and use something other than m1?

 

In the documentation it is stated that if I only config dkim2 i should be able to setup from address. In reality I can not .

 

Any idea?

 

Thanks,

Aviram

 

1 answer

1 accepted

0 votes
Answer accepted
M@ICE Atlassian Team Oct 10, 2018

Hi Aviram,

 

This is something that happens when the domain for your custom from address is already used with one of the email service providers used by Statuspage.

 

The easiest resolution for this would be to add a subdomain to your custom from address. For example using noreply@notifications.statuspage.io or noreply@status.statuspage.io would generate a different DKIM#1 hostname and allow you to set and validate your DNS records.

 

If you prefer to use your current custom from address and do not want to configure DKIM#1 send a note to hi@statuspage.io and we will be happy to set your account to only use the DKIM#2 provider to send your notification emails.

Kind regards,

Matthijs

One of you guys changed the DKIM1 to mailto._domainkey and it works fine now.

Thanks

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events