GitHub Pages: InvalidDNSError for repriza2.ro although DNS is correct #209126
Replies: 2 comments 2 replies
|
I checked repriza2.ro against public DNS and it currently returns no A or CNAME records at all, so the InvalidDNSError is actually the expected result rather than a GitHub bug. For an apex domain, you need A records on the four GitHub Pages IPs (185.199.108.153, 185.199.109.153, 185.199.110.153 and 185.199.111.153), and www should be a CNAME to ambroziandreea.github.io. Also check with your registrar that no redirect or parked-page setup is sitting in front of the DNS, since that fails the check too. Once the records actually resolve, GitHub needs some time to re-run its DNS check before you can enforce HTTPS. |
|
Solved. It was DNS propagation after the nameserver change: the DNS check turned green about 24 hours after I moved the nameservers to Cloudflare, and the certificate was issued right after. Thanks! |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Pages
Body
What I'm trying to do
Use the custom domain repriza2.ro (with www.repriza2.ro as alternate name) for my GitHub Pages site.
What happens instead
Settings → Pages shows: "Both repriza2.ro and its alternate name are improperly configured. Domain's DNS record could not be retrieved (InvalidDNSError)". The TLS certificate is stuck at "1 of 3, Certificate Requested", so I can't enable Enforce HTTPS.
DNS setup (Cloudflare, all records DNS only, not proxied)
I moved the nameservers at the registrar to haley.ns.cloudflare.com and major.ns.cloudflare.com on September 29, 2026, around 10:05 UTC. Before that, the registrar's nameservers had no records for the domain.
Public resolvers (Google DNS) return the correct A records and CNAME, and the site already opens on http://repriza2.ro.
What I already tried
Has anyone seen this before, especially with .ro domains or after moving nameservers to Cloudflare? Any idea what else I could check?
Thank you!
All reactions