[AX-348] Organization verified domain functionality is bro... - Create and track feature requests for Atlassian products.

Type: Suggestion
Resolution: Won't Fix
Component/s: Domain Verification - Initial Setup
Labels:
- collector-3183179d
- timeout-suggestion-bulk-close
Environment:

Hide

  Customer can be contacted: yes
  Location: https://coyainsure.atlassian.net/admin/o/bef6e257-0ba9-4ba8-a02a-c17a183f7946/domains
  Referrer:
  User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36
  Screen Resolution: 1920 x 1080
  Build Version: 576


Show
  Customer can be contacted: yes   Location: https://coyainsure.atlassian.net/admin/o/bef6e257-0ba9-4ba8-a02a-c17a183f7946/domains   Referrer:   User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36   Screen Resolution: 1920 x 1080   Build Version: 576

Feedback Policy:

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.

Organization verified domain functionality is broken. Its ridiculous to ask:
"Don't delete the record from your server at any time as we need to verify it on a regular basis."

TXT records for verification are only meant to be temporary, otherwise having many TXT records on your main TLD can cause issues with SPF and other TXT dependant records.

I would advice to use a subdomain like DKIM uses for a permanent records like this EG:
_attlassian.domain.com TXT verifycationThing

is related to

AX-315 Domain Verifications Fails if Too many TXT records in DNS

Closed

Assignee:: Unassigned

Reporter:: lingbo (Inactive)

Votes:: 2 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 27/Dec/2017 1:14 PM

Updated:: 3 days ago 8:56 PM

Resolved:: 28/May/2025 7:03 AM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates