DNS publication troubleshooting

Why is my DNS record not detected?

A provider can report that a TXT, CNAME or MX record is missing even after it was saved. Compare the exact issued owner, type and value with public DNS before replacing a record or changing DNS providers.

Compare an expected DNS record

Use the exact provider-issued value. Enter the full owner, record type and target/value from the service that requested the record. Do not enter passwords, account IDs, API keys or an entire zone export.

What the comparison can show

Match: the expected value is publicly visible at the requested owner.
Mismatch: an answer exists but differs from the value you supplied.
Absent: the expected type is not currently visible through the public DNS path checked.
Duplicate owner: a bounded duplicate-suffix candidate contains the expected value, which can happen when a DNS panel appends the zone name automatically.
Transient or ambiguous: DNS did not provide a stable answer; this is not treated as a missing record.

Safe repair steps

Identify the authoritative DNS host. It can be different from the registrar where the domain was purchased.
Copy the provider-issued owner and target again. For a CNAME, compare the target; for MX, include its priority; for TXT, compare the complete value.
Check whether the DNS panel expects a relative host such as selector._domainkey or a full name. Do not append the domain twice.
Preserve the current record, then change only the verified owner/type/value. Avoid deleting unrelated SPF, MX or verification records.
Recheck public DNS and then refresh the sending provider's status. A public match does not prove the provider has completed its own verification.

What this does not prove

A missing public value cannot prove that you edited the wrong panel, because delegation changes, propagation, resolver behavior and provider-side checks can also matter. A match likewise does not prove a message was signed, accepted or delivered to the inbox.