DNS
TXT record setup for verification and email authentication
A TXT record is a flexible DNS record type used by many services. Because several unrelated systems can require TXT data on the same domain, the main risk is replacing an existing record or putting a value at the wrong hostname.
Copy both the host/name and value
A provider may ask for a record at the zone apex, a selector such as `_dmarc`, or another specific label. Putting the right value at the wrong name will not satisfy the service checking it.
Do not delete unrelated TXT records
A domain may already have verification, SPF, DKIM-related, DMARC, or application records. Adding a new service usually does not mean replacing every existing TXT entry.
Watch provider-specific formatting in DNS interfaces
Some interfaces automatically append the zone name or handle quotes internally. Verify the resulting DNS answer with a lookup after saving the record.
Remove obsolete verification deliberately
Old records can create clutter and sometimes policy confusion. Keep an inventory of which service owns each TXT value so decommissioning a service includes DNS cleanup.