-
Bug
-
Resolution: Timed out
-
Low
-
None
-
Severity 2 - Major
Issue Summary
If DNS contains a large number of unique TXT record items in the root of the domain (including the Atlassian Verification), the Domain cannot be verified or re-verified during the normal checks.
Steps to Reproduce
- set up 30 TXT record entries with a lot of text in them
- Wait for the changes to propagate to our system. Please note that the change may take up to 72 hours for our system to stop caching the old results.
- Attempt to claim the domain (or reclaim it)
Expected Results
The domain claims as expected
Actual Results
The domain claim fails and the following error is thrown in the logs:
Error: queryTxt ESERVFAIL EXAMPLE.com at QueryReqWrap.onresolve [as oncomplete] (dns.js:213:19)
Notes
Domain Verification is checked on standard DNS (not EDNS) and if the Message Size is greater than 512 bytes for TXT Records, the verification can fail
Workaround
Currently, there are only two methods that can be used to bypass this issue:
1. Delete some of the TXT record entries so that the message size is less than 512 bytes
2. Use HTTPS verification instead.
[AX-315] Domain Verifications Fails if Too many TXT records in DNS
| Component/s | Original: Domain Claim - Initial Setup [ 53302 ] | |
| Component/s | New: Domain Verification - Initial Setup [ 80145 ] | |
| Key |
Original:
|
New:
|
| Support reference count | Original: 5 | |
| Symptom Severity | Original: Minor [ 16130 ] | New: Severity 2 - Major [ 14431 ] |
| Project | Original: Atlassian Guard [ 18910 ] | New: Admin Experience [ 24210 ] |
| Resolution | New: Timed out [ 10 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| Support reference count | Original: 4 | New: 5 |
| Link |
New:
This issue relates to |
| Support reference count | Original: 3 | New: 4 |
| Support reference count | Original: 2 | New: 3 |
| Description |
Original:
h3. Issue Summary
If DNS contains 28 or more unique TXT record items in the root of the domain (including the Atlassian Verification), the Domain cannot be verified or re-verified during the normal checks. h3. Steps to Reproduce # set up 30 TXT record entries with a lot of text in them # Wait for the changes to propagate to our system. Please note that the change may take up to 72 hours for our system to stop caching the old results. # Attempt to claim the domain (or reclaim it) h3. Expected Results The domain claims as expected h3. Actual Results The domain claim fails and the following error is thrown in the logs: Error: queryTxt ESERVFAIL EXAMPLE.com at QueryReqWrap.onresolve [as oncomplete] (dns.js:213:19) h3. Notes Domain Verification is checked on standard DNS (not EDNS) and if the Message Size is greater than 512 bytes for TXT Records, the verification can fail h3. Workaround Currently, there are only two methods that can be used to bypass this issue: 1. Delete some of the TXT record entries so that the message size is less than 512 bytes 2. Use HTTPS verification instead. |
New:
h3. Issue Summary
If DNS contains a large number of unique TXT record items in the root of the domain (including the Atlassian Verification), the Domain cannot be verified or re-verified during the normal checks. h3. Steps to Reproduce # set up 30 TXT record entries with a lot of text in them # Wait for the changes to propagate to our system. Please note that the change may take up to 72 hours for our system to stop caching the old results. # Attempt to claim the domain (or reclaim it) h3. Expected Results The domain claims as expected h3. Actual Results The domain claim fails and the following error is thrown in the logs: Error: queryTxt ESERVFAIL EXAMPLE.com at QueryReqWrap.onresolve [as oncomplete] (dns.js:213:19) h3. Notes Domain Verification is checked on standard DNS (not EDNS) and if the Message Size is greater than 512 bytes for TXT Records, the verification can fail h3. Workaround Currently, there are only two methods that can be used to bypass this issue: 1. Delete some of the TXT record entries so that the message size is less than 512 bytes 2. Use HTTPS verification instead. |
| Description |
Original:
h3. Issue Summary
If DNS contains 28 or more unique TXT record items in the root of the domain (including the Atlassian Verification), the Domain cannot be verified or re-verified during the normal checks. h3. Environment (Optional - If Applicable) * * h3. Steps to Reproduce # set up 30 TXT record entries with a lot of text in them # Wait for the changes to propagate to our system. Please note that the change may take up to 72 hours for our system to stop caching the old results. # Attempt to claim the domain (or reclaim it) h3. Expected Results The domain claims as expected h3. Actual Results The domain claim fails and the following error is thrown in the logs: Error: queryTxt ESERVFAIL EXAMPLE.com at QueryReqWrap.onresolve [as oncomplete] (dns.js:213:19) h3. Notes Domain Verification is checked on standard DNS (not EDNS) and if the Message Size is greater than 512 bytes for TXT Records, the verification can fail h3. Workaround Currently, there are only two methods that can be used to bypass this issue: 1. Delete some of the TXT record entries so that the message size is less than 512 bytes 2. Use HTTPS verification instead. |
New:
h3. Issue Summary
If DNS contains 28 or more unique TXT record items in the root of the domain (including the Atlassian Verification), the Domain cannot be verified or re-verified during the normal checks. h3. Steps to Reproduce # set up 30 TXT record entries with a lot of text in them # Wait for the changes to propagate to our system. Please note that the change may take up to 72 hours for our system to stop caching the old results. # Attempt to claim the domain (or reclaim it) h3. Expected Results The domain claims as expected h3. Actual Results The domain claim fails and the following error is thrown in the logs: Error: queryTxt ESERVFAIL EXAMPLE.com at QueryReqWrap.onresolve [as oncomplete] (dns.js:213:19) h3. Notes Domain Verification is checked on standard DNS (not EDNS) and if the Message Size is greater than 512 bytes for TXT Records, the verification can fail h3. Workaround Currently, there are only two methods that can be used to bypass this issue: 1. Delete some of the TXT record entries so that the message size is less than 512 bytes 2. Use HTTPS verification instead. |
| Description |
Original:
h3. Issue Summary
If DNS contains 28 or more unique TXT record items in the root of the domain (including the Atlassian Verification), the Domain cannot be verified or re-verified during the normal checks. h3. Environment (Optional - If Applicable) * * h3. Steps to Reproduce # set up 30 TXT record entries with a lot of text in them # Wait for the changes to propagate to our system. Please note that the change may take up to 72 hours for our system to stop caching the old results. # Attempt to claim the domain (or reclaim it) h3. Expected Results The domain claims as expected h3. Actual Results The domain claim fails and the following error is thrown in the logs: Error: queryTxt ESERVFAIL EXAMPLE.com at QueryReqWrap.onresolve [as oncomplete] (dns.js:213:19) h3. Notes 11 records is not enough to generate the issue. The threshold for the issue starts somewhere between 11 and 28 records. h3. Workaround Currently, there are only two methods that can be used to bypass this issue: 1. Delete some of the TXT record entries to 11 or below. 2. Use HTTPS verification instead. |
New:
h3. Issue Summary
If DNS contains 28 or more unique TXT record items in the root of the domain (including the Atlassian Verification), the Domain cannot be verified or re-verified during the normal checks. h3. Environment (Optional - If Applicable) * * h3. Steps to Reproduce # set up 30 TXT record entries with a lot of text in them # Wait for the changes to propagate to our system. Please note that the change may take up to 72 hours for our system to stop caching the old results. # Attempt to claim the domain (or reclaim it) h3. Expected Results The domain claims as expected h3. Actual Results The domain claim fails and the following error is thrown in the logs: Error: queryTxt ESERVFAIL EXAMPLE.com at QueryReqWrap.onresolve [as oncomplete] (dns.js:213:19) h3. Notes Domain Verification is checked on standard DNS (not EDNS) and if the Message Size is greater than 512 bytes for TXT Records, the verification can fail h3. Workaround Currently, there are only two methods that can be used to bypass this issue: 1. Delete some of the TXT record entries so that the message size is less than 512 bytes 2. Use HTTPS verification instead. |
| Support reference count | Original: 1 | New: 2 |