GitHub Pages verification not detecting TXT record despite DNS being correct

[swantron]

Select Topic Area

Question

Body

I'm experiencing a GitHub Pages domain verification issue where the verification system cannot detect a correctly configured TXT record.

Domain: swantron.com
Repository: swantron/swantron
TXT Record: _github-pages-challenge-swantron.swantron.com
Expected Value: d32e46be6b94503a960b403cda1299

Issue:
Both repository-level and account-level verification are stuck on "unverified" status, despite the TXT record being correctly configured and resolving globally from all authoritative nameservers.

DNS Evidence:
All 4 Google nameservers (ns-cloud-e1 through e4) return the correct TXT record value. The record also resolves correctly from Google DNS, Cloudflare DNS, and OpenDNS.

What I've Tried:

• Verified DNS configuration is correct
• Confirmed TXT record resolves globally
• Tried repository-level verification
• Tried account-level verification
• Updated TXT record value to match current challenge
• Multiple removal/re-add attempts

Support Case: [https://support.github.com/ticket/personal/0/4023728]

Has anyone else experienced this? Is there a known issue with GitHub's verification checker and Google Domains nameservers?

@github/support - Can you help escalate this?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐