Seems like bounces.mail-us.atlassian.net is an incorrect DNS record Atlassian requires in a custom email domain set up. Tiny problem: that domain name doesn't exist. bounces.mail.atlassian.net does though, but that is not accepted.
Yes, tried to add bounces.mail.atlassian.net earlier, and that resolves. But then the DNS check fails cause it expects bounces.mail-us.atlassian.net.
Will open a ticket.
Thanks,
A
Dear @Andreas Dahlström
Got it, yes, the best is to open a support ticket.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Andreas Dahlström
Did you try to delete and remake the TXT record completely?
After that, you should wait for the propagation.
Also, look at this Troubleshooting page, maybe this will help.
https://support.atlassian.com/organization-administration/docs/troubleshoot-custom-domains/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I've remade all fields several times without any luck? And why just the TXT?
The real problem is that the bounces.mail-us.atlassian.net (which I think is a generic one) doesn't resolve. Seems like a bug to me
Thanks,
A
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear @Andreas Dahlström
For most users, the correct record should be:
bounces.mail.atlassian.net
not bounces.mail-us.atlassian.net
.
Did you also try this record?
If the issue persists, the best is to create a support ticket on Atlassian to fix the incorrect CNAME requirement on their side. Open a ticket via:
https://support.atlassian.com/contact/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.