Pages custom domain: InvalidDNSError and Dnsruby::ServFail, while Google and Cloudflare resolve correctly #209374
Replies: 1 comment
|
Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided. This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello! We cannot obtain a GitHub Pages HTTPS certificate for zolotaya-vilka.ru. Repository: https://github.com/papakult/zolotaya-vilka. Deployment uses GitHub Actions and completes successfully. HTTP serves the site, but HTTPS presents a *.github.io certificate that does not cover the custom domain.
DNS configuration: nameservers ns1.reg.ru and ns2.reg.ru; apex A records 185.199.108.153, 185.199.109.153, 185.199.110.153, 185.199.111.153; www CNAME papakult.github.io. Google Public DNS and Cloudflare return these records. Apex AAAA, CAA and DS queries return no records without an error.
The Pages health API reported dns_resolves=false, is_https_eligible=false, InvalidDNSError (Domain's DNS record could not be retrieved), and caa_error=Dnsruby::ServFail for the apex and www. The UI shows DNS check unsuccessful.
We have removed and re-added the custom domain and redeployed successfully, but HTTPS is still unavailable. There is a separate light-version repository using Vercel; Pages is not enabled there, and the custom domain is configured on the main repository only. We have also opened a ticket with the DNS provider.
How can we determine which DNS lookup is failing for GitHub's resolver? Is there a known issue with REG.RU authoritative DNS or a way to get more detailed Pages DNS diagnostics? We would appreciate a specific diagnostic step before changing nameservers or hosting.
All reactions