TXT records commonly publish service verification and email-authentication values and must be copied with exact syntax.
Applies to: Nameservers and DNS records
DNS tells internet services where to find a website, mail server or other service. Changes can be technically correct yet appear inconsistent for a time because recursive resolvers cache earlier answers until their TTL expires.
Before you start
- Confirm that you are authorised to manage the domain and identify its authoritative DNS provider.
- Export or record the complete current DNS zone and previous TTL values before making changes.
Step-by-step
- Identify the record name separately from the value. A provider may display @, a selector such as selector1._domainkey, or a verification label.
- Copy the complete value without smart quotes, hidden line breaks or explanatory text from the provider page.
- Let the DNS control panel manage surrounding quotation marks unless its documentation says otherwise.
- When a long value is split into quoted strings by the DNS server, verify the combined public answer rather than assuming the split is an error.
- Do not delete unrelated TXT records at the same name. Multiple verification records can coexist, while SPF requires special handling to avoid multiple conflicting SPF policies.
- Query the exact record name publicly and complete the provider's verification step.
Confirm the result
- The public TXT answer matches the provider value semantically and the verification or mail-authentication test passes.
Common problems
| Symptom | Likely cause | What to do |
|---|---|---|
| The provider cannot find the record. | The name was entered with the domain duplicated or the record was added to a non-authoritative DNS service. | Check delegation and query the exact fully qualified name from an authoritative nameserver. |
| SPF reports multiple records. | More than one TXT value begins with v=spf1 at the same domain. | Merge authorised senders into one valid SPF policy rather than publishing a second SPF record. |
When to contact Tudor Internet
Open a ticket through the Customer Portal when the checks above do not resolve the issue, when an action is unavailable for your service, or when continuing could risk data loss or service interruption. Include the following so the request can be investigated efficiently:
- The full domain name
- The current and intended registrar or nameservers
- Any registry or transfer error shown
- Whether website or email service is currently live
Do not send passwords, private keys, full payment-card details, one-time authentication codes or unredacted identity documents in an ordinary support reply.
Related articles
- Manage DNS records
- Set up SPF, DKIM and DMARC records
- Check DNS with dig, nslookup and public resolvers
- Create and troubleshoot MX records
- Create and troubleshoot A and AAAA records
Last reviewed: 2026-07-18.
