You paste these values into the DNS records page of whoever hosts your domain's DNS. That's often your domain registrar, but it can be your website host or a service like Cloudflare. Each record is a TXT record, which is a general text entry.1
Finding the right place
DNS hosting is wherever your domain's name servers point. If you're unsure, the registrar's control panel is the usual starting point, and it will tell you if DNS is handled elsewhere.
Look for a page called DNS, DNS records or Manage DNS. Then add a new record and choose the type TXT. Google's own instructions say help with a domain provider's settings has to come from that provider, because Google doesn't provide technical support for third-party domain providers.2 Your DNS host's help pages are the right guide for button names.
The fields
Most DNS hosts show the same three boxes.
- Type is TXT.
- Name (also called host) is where the record sits. For SPF, that's the bare domain. Many hosts use
@for that. For DKIM it ends in._domainkey, and for DMARC it's_dmarc. - Value (also called content or text) is the string your mail service or this site's other pages describe.
Some hosts add your domain to the name automatically. If you type the full name too, you can end up with it doubled. Look at the example your host shows.
Several TXT records at one name
A domain can have more than one TXT record, if the DNS server supports that.1 But the SPF standard warns you to beware of other TXT records at the same name.3 If you already have an SPF line, edit it rather than adding a second one, since a domain should publish only one. The SPF page shows what the line contains.
A single record can also hold more than one character string.1 Long DKIM keys are often split that way. Your DNS host will normally handle the splitting for you, or tell you how.
Why changes don't show straight away
Each DNS record carries a TTL, short for Time to Live. Cloudflare's documentation says it controls how long each record is cached. A longer TTL means updates take longer to go into effect.4
Caches sit between you and the rest of the world. Cloudflare's page adds that it may take longer than five minutes to actually see a change, because your own local DNS cache can lag.4
Mail services can be slower still. One example from Google's DKIM help is that its admin console might keep showing an old message for up to 48 hours.2 That's the maker's wording for its own console, not a promise about every host.
If a record isn't visible yet, wait and look again. Don't keep re-adding it. Once it's saved, a lookup shows what the wider internet sees.
Where the facts come from
- TXT record, Wikipedia
- Set up DKIM, Google Workspace Admin Help
- RFC 7208: Sender Policy Framework (SPF), IETF
- Time to Live (TTL), Cloudflare DNS docs