InvalidDNSError for calonders.ru on GitHub Pages - DNS correctly configured and propagated

[CalonderA]

🏷️ Discussion Type

Bug

Body

I've been trying to connect my custom domain calonders.ru to my GitHub Pages site (CalonderA/bashkur) for over 24 hours, but I keep getting the same error:

Both calonders.ru and its alternate name are improperly configured
Domain's DNS record could not be retrieved (InvalidDNSError)

DNS Configuration
My DNS records are configured correctly with Selectel:

A records for calonders.ru (apex domain):

185.199.108.153

185.199.109.153

185.199.110.153

185.199.111.153

CNAME record for www.calonders.ru:

calondera.github.io.

DNS Propagation Verified
I've verified propagation globally using multiple DNS checkers (dnschecker.org, whatsmydns.net). All 4 IP addresses are visible worldwide. Screenshot attached.

What I've already tried:
Removed and re-added the custom domain in Settings → Pages (multiple times with 10-15 min waits)

Verified CNAME file in repository root contains exactly: calonders.ru

Waited over 24 hours

Cleared local DNS cache and browser cache

Tried different browsers

Repository Info:
Repository: CalonderA/bashkur

GitHub Pages URL: https://calondera.github.io/bashkur/

Custom Domain: calonders.ru

The DNS is correct and fully propagated. I believe this is a GitHub-side issue where the validation process is stuck. Can someone help me get this resolved, or does anyone know of any additional steps I can try?

[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. ⭐

[v-ember]

Hi @CalonderA , thanks for posting in GitHub Discussions!

The Repositories category is meant for questions related to repositories on GitHub. A repository contains all of your project's files and each file's revision history. I've gone ahead and moved this post to our Other category, as this topic may be more relevant there and might help someone give you a nudge in the right direction. 😁

[asp53826]

I checked this from outside your DNS provider, and the current public state points to DNS delegation plus Pages configuration rather than a stuck GitHub validation job.

Right now:

• dig +short NS calonders.ru, A calonders.ru, and CNAME www.calonders.ru return no answers.
• Both Cloudflare and Google public DNS return SERVFAIL for the domain.
• GitHub's Pages API shows CalonderA/bashkur is built at https://calondera.github.io/bashkur/, but its saved custom-domain value is currently null.

That means records may exist inside the Selectel zone editor, but public resolvers cannot reach a working authoritative zone for calonders.ru. First check the domain at the registrar, not only the Selectel DNS panel:

1. Confirm the domain is active and its registrar-level nameserver delegation exactly matches the nameservers Selectel assigned to this zone.
2. If the registrar already shows those nameservers, ask Selectel why the delegation returns SERVFAIL.
3. Do not continue until these return real answers from an unrelated network:

dig +short NS calonders.ru
dig +short A calonders.ru
dig +short CNAME www.calonders.ru

The A answers should be GitHub's four 185.199.108-111.153 addresses, and www should point directly to calondera.github.io.

There is a second issue: this repository publishes Pages with a custom GitHub Actions workflow. GitHub's documentation says an existing repository CNAME file is ignored in that mode. Once DNS resolves publicly, go to Repository Settings → Pages, enter calonders.ru under Custom domain, and save it there. Avoid repeatedly removing it while DNS is broken, because that restarts validation.

GitHub documents both details here:

• https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site
• https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/troubleshooting-custom-domains-and-github-pages

After the NS/A/CNAME checks work, allow the documented propagation window and then enable HTTPS. If you post the registrar's configured nameservers after updating them, they can be checked directly.