Troubleshooting
apex_txt_missing
The apex A records are right, but the _apexly TXT record that proves control is missing or different.
Seen in pending_dnsFix is on the customer's sideAuto-recovers
What it means
For an apex domain the A records route traffic, but anyone can point A records at a shared address. The TXT record at _apexly.<hostname> proves that the person who controls the zone asked for this domain. We found the right A records and either no TXT record there or one with a different value.
ExpectedTXT_apexly → apexly-verify=k2Pq…
FoundTXT_apexly → (no record)
The exact name and value are in dns.apex.txt in the domain object.
Why it happens
- The customer added the A records and missed the second record.
- The TXT record went on the apex itself (
@) instead of on_apexly. - The value was copied with quotes or a trailing space. Most providers add quotes themselves.
- The domain was deleted and created again, which issues a new value; the old TXT record no longer matches.
What to do
- Ask the customer to add the TXT record exactly as shown, on the name
_apexly. - Keep the A records as they are.
- We check every 15 seconds; the domain moves on as soon as both records match.
Was this helpful?
Edit this page