Two jobs that happen to use DNS

When you connect a domain to an email provider, the provider may ask you to add a TXT record. This is usually a domain-verification record: a unique value that the provider looks up in DNS to confirm that you can change the domain’s settings. It helps the provider decide whether to let your account use the domain. It does not, by itself, tell other mail systems that messages from your domain are legitimate.

Email authentication records do that second job. SPF identifies servers permitted to send mail for a domain. DKIM publishes a public key that receiving systems can use to check a message’s signature. DMARC tells receivers how to evaluate messages that fail checks involving SPF or DKIM and whether those checks align with the domain shown in the visible From address. These records also live in DNS, often as TXT records, but they have different names, values and purposes.

How to recognize a verification record

A verification TXT value is typically supplied by one provider for one domain setup. It might resemble provider-verify=YOUR-ASSIGNED-VALUE, where the final part is a placeholder for the value the provider gives you. The provider will specify where to publish it: sometimes at the root of the domain, and sometimes at a named subdomain. Use the exact host and value from its instructions rather than guessing from the example.

A verification token is not an email password or an API key, but it is still worth handling carefully. Share the minimum information needed when asking for help, and never include account credentials in a DNS record or troubleshooting screenshot. Some providers use a CNAME record or another method for verification instead of TXT; follow the method requested for the service you are configuring.

Once the provider has checked the record, its instructions should guide whether to leave it in place. A provider may check ownership again later. Removing a verification record simply because the initial check succeeded can therefore cause a future connection problem, even though it does not directly change how SPF, DKIM or DMARC work.

How authentication records differ

An SPF record is a TXT record whose value begins with v=spf1. It lists authorized sending sources using mechanisms defined by SPF. A domain should have one SPF record at a given DNS name; adding a second SPF TXT record there can make SPF evaluation fail. If two services send mail for the same domain, their requirements generally need to be combined into one carefully constructed SPF record, subject to SPF’s limits.

A DKIM public key is commonly published as a TXT record at a name such as selector1._domainkey.example.com. The selector distinguishes one key from another, so a domain can have DKIM records for different services or keys at different selectors. The sending service holds the private key and signs outgoing messages. The private key does not belong in public DNS. Some services use a CNAME at the selector instead and manage the public key at its destination.

A DMARC record is published at _dmarc.example.com and begins with v=DMARC1. Its policy tells receiving systems what the domain owner requests when a message fails DMARC evaluation. SPF or DKIM can contribute to a DMARC pass when the relevant authenticated domain aligns with the visible From domain. DMARC configuration is separate from provider verification: a provider can verify your domain even if its outgoing messages are not yet configured to authenticate as you intend.

Add records without replacing unrelated settings

In a DNS editor, check both the record type and the full name the provider expects. Some editors ask for the complete name, such as _dmarc.example.com; others ask only for the part before the domain, such as _dmarc. Entering the full domain into the second kind of editor may create an unintended name. Check the resulting DNS name after saving rather than relying only on what you typed.

Several unrelated TXT records can coexist at the domain root. For example, a verification token and an SPF record can both be present there. Do not delete an existing TXT record just because you are adding another. Equally, do not paste a verification token into an SPF value or combine separate purposes into one string. If the editor offers multiple text fields for one record, distinguish that feature from creating separate TXT records.

A practical check when setup stalls

If verification fails, first confirm that you edited the DNS zone used by the domain’s authoritative nameservers. Then check the exact record name, type and value requested by the provider, including punctuation. DNS changes may not appear everywhere immediately because cached answers can persist for a while. Wait and retry the provider’s check before changing a record that appears correct.

If verification succeeds but sent mail still fails authentication, investigate SPF, DKIM and DMARC separately. Confirm that the actual sending service is covered by the intended SPF setup, that its DKIM selector resolves as instructed, and that the visible From domain aligns with an authentication result where needed. Treat a successful ownership check as permission to proceed with setup, not as proof that every outgoing message is authenticated.

Back to category ↗