Uploaded image for project: 'Atlassian Access'
  1. Atlassian Access
  2. ACCESS-1142

Provide additional methods to claim a domain (CNAME record for a sub-domain)

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      Thanks everyone for watching and commenting on this ticket.

      As part of an initiative to consolidate feature requests/suggestions to gather centralized feedback, improving the popularity of the existing ones, we are closing this ticket as Won't Do as we didn't have a considerable number of users seeking for this feature in the past year.

      Adding some data here, there were:

      • 3 support tickets
      • 15 votes

      As always, thank you for the opportunity to improve our products, Feel free to bring additional feedback via existing suggestions!

      João N.,
      Atlassian Team

      At this moment, the only possibilities to claim a domain in Atlassian are either a DNS TXT record on the main (root) domain, or a file placed on the webserver's root page (HTTPS method).

      These methods have the disadvantage of releasing this information to the public: Everyone on the internet can check if example.com is claimed in Atlassian. This creates an additional security risk for targeted phishing emails.

      Please provide an alternative domain verification method using a CNAME record for a subdomain of example.com.

      Example:

      <random-string-1>.example.com IN CNAME <random-string-2>.atlassian.com
      

      Where both random-string-1 and random-string-2 are generated by Atlassian inside the organization and the domain to be claimed is example.com.

      Attachments

        Issue Links

          Activity

            People

              asridhara Adarsh
              clionte Claudiu Lionte (Inactive)
              Votes:
              15 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: