Custom domain stuck: "NotServedByPagesError" although DNS is correct #213094
Replies: 3 comments
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
|
Hi @aagorlan, Based on the information you've provided, your DNS configuration appears consistent with GitHub Pages' documented requirements. The four apex A records and the Here are a few additional checks worth trying: 1. Verify DNS resolution from multiple resolvers dig sezonaapp.com A @1.1.1.1
dig sezonaapp.com A @8.8.8.8
dig www.sezonaapp.com CNAME
dig sezonaapp.com CAAThe CAA check is particularly useful because restrictive CAA records can interfere with certificate issuance. 2. Check whether HTTPS provisioning is blocked Since the certificate remains at "1 of 3 — Certificate Requested", the certificate provisioning process may not have completed. Check whether any CAA records restrict the certificate authorities GitHub Pages uses. 3. Check for DNSSEC-related issues You can test DNSSEC validation using: dig sezonaapp.com A +dnssec
dig sezonaapp.com A @1.1.1.1If DNSSEC is configured incorrectly, some resolvers may fail even when others return the expected records. 4. Verify the Pages deployment configuration Under Repository → Settings → Pages, confirm that:
5. Escalate to GitHub Support Since you've already waited more than 24 hours, verified your DNS records, and removed/re-added the domain, this may require investigation on GitHub's side. GitHub Support: Include:
One additional question: Does Those details could help distinguish a certificate issuance issue from a DNS validation problem. Hope this helps! |
|
Checking When you removed and re-added To force a fresh DNS validation and ACME certificate order, remove |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Pages
Body
Hi,
My GitHub Pages site aagorlan/sezona has the custom domain sezonaapp.com. The DNS check keeps failing with "Both sezonaapp.com and its alternate name are improperly configured — Domain does not resolve to the GitHub Pages server (NotServedByPagesError)", and the TLS certificate is stuck at "1 of 3 — Certificate Requested".
The DNS has been correct for more than a day:
nslookup sezonaapp.com 8.8.8.8returns exactly the four GitHub Pages addresses, and global DNS checkers show the same.The site is served by GitHub Pages over HTTP, and www redirects correctly. The CNAME file in the repository contains "sezonaapp.com".
Another domain of mine, sezonaapp.ru (repository aagorlan/sezona-ru), uses the same nameservers and the same records; it passed the DNS check at once and has a valid certificate with HTTPS enforced.
I have already removed and re-added the custom domain once; nothing changed. It looks like the first check, made before the records existed, is cached. Could you please re-run the DNS check and the certificate issuance for sezonaapp.com?
Thank you!
All reactions