HTTPS certificate provisioning stuck with InvalidDNSError for dvs-servis75.ru

[sapfirrrr]

🏷️ Discussion Type

Bug

Body

Hello, my custom domain dvs-servis75.ru is working over HTTP, but HTTPS certificate provisioning fails with InvalidDNSError. DNS records are configured correctly (4 A records to GitHub Pages IPs, CNAME for www). Please manually re-trigger the Let's Encrypt certificate issuance for my domain. Repository: https://github.com/sapfirrrr/dvs-chita/

What is the URL of the repository you are having issues with?
https://github.com/sapfirrrr/dvs-chita/

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

[MDansevicius]

I would double-check the DNS records for any conflicting entries, especially because GitHub mentions that extra A/AAAA/ALIAS/ANAME records can prevent HTTPS certificate provisioning.

For dvs-servis75.ru, the apex domain should have only these GitHub Pages A records:

185.199.108.153
185.199.109.153
185.199.110.153
185.199.111.153

And www should be a CNAME pointing to:

sapfirrrr.github.io

Also check for:

extra A/AAAA records
conflicting ALIAS/ANAME records
wildcard DNS records
CAA records that don't allow letsencrypt.org

If the DNS was recently corrected, try removing and re-adding the custom domain in GitHub Pages. GitHub specifically recommends this to trigger HTTPS provisioning again after DNS changes.

You can verify the records with dig or Resolve-DnsName and make sure there are no unexpected records being returned.