DNS publication troubleshooting

DNS record not detected after saving the provider-issued value

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.

Problem description

Your sending provider cannot verify the expected DNS record:

DNS record not detected after saving the provider-issued value.

Run this automated test on my domain

Enter your domain. MailFixIt checks the relevant DNS records automatically and shows the evidence.

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.

Frequently asked questions

Why is my DNS record not detected after I saved it?

The owner, type or value may differ from the provider-issued record; the zone may have been appended twice; the active authoritative DNS host may differ from the registrar; or DNS may still be updating. Public absence alone does not prove which occurred.

What does a duplicate DNS owner mean?

It is a bounded indication that the expected name may also have been published with the zone appended twice, such as selector._domainkey.example.com.example.com. Check the DNS host’s relative-name syntax before recreating it.

Should I delete the existing record before fixing it?

Preserve the existing value and its TTL for rollback first. Remove or replace only the intended record after confirming every service that depends on it.

Related email diagnostics

Email delivery delayed or rejected after a DNS migrationDiagnose email that stopped arriving after a DNS change. Compare public MX records with the intended provider and avoid false alarms for mail gateways. Cloudflare: DKIM CNAME records are not resolving as expectedDiagnose a Cloudflare DKIM CNAME that is not verifying. Compare the provider-issued CNAME with public DNS and safely check whether CNAME flattening is hiding it.

Primary sources: RFC 1035 domain names.