-
Type:
Suggestion
-
Resolution: Won't Fix
-
Component/s: Domain Verification - Initial Setup
-
Environment:
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
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
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
-