Configure DNS TXT Record

The Problem

A platform is asking you to add a TXT record to verify domain ownership or enable a feature, and TXT records are fussy about exact formatting — one extra space or missing quote and the verification silently fails.

About this problem

TXT records hold arbitrary text data attached to a domain, used for all sorts of things — domain ownership verification for Google Workspace or a hosting platform, SPF records for email, or various service-specific proof-of-ownership strings. Because the format is free text rather than a structured field, they're surprisingly easy to get subtly wrong: trailing whitespace, missing quote marks some providers require, or adding it to the wrong hostname (root vs a specific subdomain).

This comes up constantly when connecting a new third-party service, verifying a domain with a search console or site-verification tool, or setting up email authentication.

What's Included

• Confirming the exact TXT value and target hostname required by the service asking for it
• Adding the record with correct formatting for your specific DNS provider
• Checking for conflicts with existing TXT records on the same hostname
• Verifying the record resolves correctly and the requesting service recognises it

What's NOT Included

• Writing the TXT value itself — that comes from whatever service is requesting verification
• SPF/DKIM/DMARC strategy and content (see the dedicated email authentication services)
• Ongoing management of multiple TXT records across many services

How It Works

1. Get the exact TXT record value and target host from the service requesting it, copied precisely, not retyped.
2. Check for existing TXT records on the same host that might need to coexist rather than be overwritten.
3. Add the record with your DNS provider's correct formatting (quoting conventions vary by provider).
4. Verify the record resolves correctly using a DNS lookup tool.
5. Confirm with the requesting service that verification now succeeds.

In practice: you buy the service, send over whatever access or details the job needs, I investigate and do the work, and you confirm it's resolved before we call it done.

Frequently Asked Questions

What is a TXT record used for?

It stores text data attached to your domain, commonly used for domain ownership verification, SPF email records, and various service-specific proof strings.

Why does my domain verification keep failing even though I added the TXT record?

The most common causes are a typo or extra character in the value, it hasn't propagated yet, or it was added to the wrong hostname.

Can I have multiple TXT records on the same domain?

Yes, multiple TXT records can coexist on the same hostname — they don't overwrite each other unless your DNS provider's interface replaces rather than adds.

How long does a TXT record take to verify?

Propagation itself is usually quick, but some services only check periodically, so verification can sometimes take longer than the DNS change itself.

Do TXT records expire?

No, a TXT record stays until you remove it — it's not time-limited, though some are only needed temporarily for one-off verification and can be cleaned up afterwards.

Can a TXT record break my email?

Only if it conflicts with or is mistaken for an SPF record on the same hostname — multiple SPF-like TXT records on one domain can cause authentication issues, so care's needed there specifically.