How to Add a TXT Record Without Formatting Mistakes

The host field is where most TXT record mistakes happen. A verification record almost always goes on @ (the root), while an SPF record also typically belongs on @ since it governs the whole domain's outgoing mail. DKIM, by contrast, uses a specific selector prefix supplied by the email provider, such as selector1._domainkey or google._domainkey, which must be entered exactly as given rather than guessed.

A frequent error is typing the full domain name into the host field when the panel already appends it automatically — entering 'selector._domainkey.yourdomain.com' in a field that only expects 'selector._domainkey' results in a record on the wrong, doubled-up hostname that the intended lookup will never find.

DKIM (DomainKeys Identified Mail) works by publishing a public cryptographic key as a TXT record at a selector-prefixed host, while the sending mail server holds the matching private key and signs each outgoing message. Receiving mail servers look up the public key via DNS and confirm the signature matches, proving the message wasn't altered in transit and genuinely came from an authorized sender.

DKIM values are long strings of what looks like random characters, often exceeding what a single DNS TXT entry technically allows in one unbroken chunk — some panels handle this by automatically splitting the value across multiple quoted strings that resolvers reassemble. Pasting the full value exactly as the email provider gives it, without adding line breaks manually, avoids breaking that structure.