Summary
To regenerate a GPT TXT record after removal from DNS, a multi-faceted approach is recommended. Google re-verifies DNS periodically, so waiting for it to fail can prompt a new key. Clear DNS and browser caches and use DNS lookup tools to confirm the old record is gone. Check DNS records on the domain management page, not after clicking into a domain. If problems persist, explore alternative verification methods or contact GPT/domain provider support for assistance. Consider deleting and re-adding the GPT. Key points include ensuring the correct domain/subdomain is selected, understanding DNS propagation delays and TTL values, using passive DNS tools, and checking for any issues with the domain provider. Verified GPT records may not always need to remain in DNS.
Key findings
- Google Re-verification: Google re-verifies DNS records periodically; waiting for a failed validation might trigger a new key.
- DNS & Cache: Clearing DNS and browser caches can resolve issues with outdated DNS information.
- Lookup Tools: Utilize DNS lookup tools (dig, nslookup, MXToolbox) to verify the old TXT record is no longer present.
- Support Channels: Contact GPT and/or domain provider support for assistance, especially if problems persist.
- Alternative Methods: Explore alternative verification methods like HTML file upload or meta tags.
- GPT Record Persistence: Once a GPT TXT record is verified, it may not need to remain in the DNS.
Key considerations
- Domain Selection: Double-check the correct domain and subdomain are selected in the GPT platform.
- DNS Propagation Time: Allow sufficient time for DNS changes to propagate (up to 48 hours) after removing the old record.
- TTL Values: Lower TTL values can speed up DNS propagation; consider setting a lower TTL in advance.
- Record Placement: Ensure the TXT record is added to the correct DNS zone (root domain or specified subdomain).
- Domain Management Location: Check domain verification status on domain management page
- Passive DNS Tools: Use passive DNS tools to recover previous records
- Deletion and Re-Adding: Consider deleting the GPT and re-adding it.
What email marketers say
12 marketer opinions
When regenerating a GPT TXT record after removal from DNS, several approaches can be taken. These include waiting for Google to re-verify the DNS, clearing DNS and browser caches, utilizing DNS lookup tools to confirm record removal, and exploring alternative verification methods. Contacting GPT support or the domain provider can also assist. Common pitfalls include adding the TXT record to the wrong domain/subdomain and DNS propagation delays. Double-checking the correct domain is selected and ensuring the old record is fully removed are important steps.
Key opinions
- Re-verification Timing: Google re-verifies DNS records periodically (approximately every 30 days). Waiting for a failed validation can prompt a new key.
- Cache Clearing: Clearing DNS and browser caches can resolve issues related to outdated DNS information.
- Verification Tools: Tools like MXToolbox or Google Admin Toolbox help confirm the TXT record's removal.
- Alternative Methods: Explore alternative verification methods like HTML file upload or meta tags if TXT record verification fails.
- Contact Support: Contacting GPT support can expedite manual reset of the verification status.
Key considerations
- Domain Selection: Ensure the correct domain is selected in the GPT platform.
- Record Placement: Add the TXT record to the correct DNS zone (root domain or specified subdomain).
- DNS Propagation: Allow sufficient time for DNS changes to propagate fully.
- Support Contact: Contact your domain provider's support for potential issues on their end.
- Passive DNS Tools: Use passive DNS tools to recover previous records
- Delete and Re-Add: Consider deleting the GPT and re-adding it.
Marketer view
Email marketer from StackOverflow shares if TXT record verification is problematic, explore alternative verification methods offered by GPT, such as HTML file upload or meta tag verification.
7 Mar 2022 - StackOverflow
Marketer view
Email marketer from Twitter suggests contacting your domain provider’s support to check if there are any issues on their end that might be preventing the TXT record from being removed or updated correctly.
20 Nov 2021 - Twitter
What the experts say
2 expert opinions
When dealing with GPT TXT records, experts suggest that once a record is verified, maintaining it in the DNS might not be essential. Additionally, it's crucial to confirm the removal of any previous TXT records using online tools before attempting to regenerate them.
Key opinions
- Post-Verification Necessity: Verified GPT TXT records might not always need to remain in DNS.
- Pre-Generation Verification: Verifying the removal of old TXT records before generating new ones is essential.
Key considerations
- Record Maintenance: Evaluate whether a verified GPT TXT record needs to be continuously maintained in DNS.
- Tool Usage: Utilize online tools to confirm the deletion of previous TXT records.
Expert view
Expert from Email Geeks shares that once a GPT TXT record is verified, it might not be necessary to keep the string in the DNS.
25 Dec 2024 - Email Geeks
Expert view
Expert from Word to the Wise forum user 'dwmw' explains using online tools to verify the TXT record is no longer present before attempting to regenerate it.
1 May 2025 - Word to the Wise
What the documentation says
5 technical articles
Documentation highlights the process of re-verifying a domain after a GPT TXT record is removed. It's essential to recognize that Google will detect the removal, necessitating a new TXT record. DNS propagation delays (up to 48 hours) should be considered, ensuring the old record is fully gone before re-adding. Utilize DNS lookup tools to confirm record removal. Understanding TTL values is also important; lower TTLs speed up propagation. If available, GPT's API can programmatically check verification status and trigger re-verification.
Key findings
- Re-verification Required: Removing the TXT record will require re-verification via a new record.
- DNS Propagation: DNS changes require time to propagate; ensure the old record is fully removed.
- Lookup Tools: DNS lookup tools confirm TXT record removal.
- TTL Awareness: Lower TTL values lead to faster DNS changes.
- API Utilization: GPT's API (if available) enables programmatic verification and re-verification.
Key considerations
- Time Allowance: Allow sufficient time for DNS propagation before attempting to re-verify.
- Tool Availability: Use DNS lookup tools to confirm TXT record removal.
- API Documentation: Consult GPT API documentation for available re-verification endpoints.
- TTL Configuration: Consider setting a lower TTL value in advance for quicker DNS updates.
Technical article
Documentation from Official GPT Help Guides suggests using GPT's API (if available) to programmatically check the domain's verification status or trigger the re-verification process. Consult the GPT API documentation for available endpoints.
15 Apr 2024 - GPTHelp.com
Technical article
Documentation from Google Workspace Admin Help explains that if the TXT record is removed, Google will eventually detect this and the domain will no longer be verified. You'll need to re-verify by adding a new TXT record.
25 Apr 2023 - Google Workspace Admin Help
How can I use DMARC to prevent spammers from using my domain?
How do I add a TXT record to a DNS configuration for Google Postmaster?
How do I configure DNS records to send emails from two different ESPs using the same subdomain?
How do I properly set up SPF and DKIM records for email marketing, including handling multiple SPF records, IP ranges, bounce capturing, and Google Postmaster Tools verification?
How do I set up DNS records for GoDaddy, Outlook, Gmail, and Yahoo to be ready for email authentication updates?
How to add DKIM record for owned domain in Salesforce Marketing Cloud (SFMC)?
