"DNS Check in Progress" Quick Guide - LawtonChilesRedCrossClub/website GitHub Wiki
🚧 Stuck on “DNS Check in Progress” — Quick Guide
Use this page when GitHub Pages shows DNS Check in Progress or HTTPS unavailable after setting a custom domain.
Applies to:
- Registrar: Porkbun
- DNS: Cloudflare
- Hosting: GitHub Pages
1) Confirm Nameservers at Porkbun
- Porkbun → Domain Management → your domain → Details ▾ → Authoritative Nameservers
- Only the two Cloudflare nameservers are listed (example:
miles.ns.cloudflare.com,raina.ns.cloudflare.com). - If Porkbun shows its own nameservers or a mix, replace with Cloudflare’s and save.
Do NOT manage DNS records at Porkbun once Cloudflare nameservers are set.
2) Remove Any Porkbun DNS Records
- In Porkbun’s DNS panel, delete default records like
ALIAS lchsredcross.org → pixie.porkbun.comandCNAME *.lchsredcross.org → pixie.porkbun.com. - These will conflict. Cloudflare should be the only place with active DNS records.
3) Rebuild Correct Records in Cloudflare
Cloudflare → DNS → Records
Required
- CNAME:
www→lawtonchilesredcrossclub.github.io(Proxied = ON) - A (4 total, name
@):185.199.108.153185.199.109.153185.199.110.153185.199.111.153
(Proxied = ON)
Common mistakes to avoid
- Don’t point
wwwto the repo URL. It must point to the org domainlawtonchilesredcrossclub.github.io. - Don’t add a CNAME at the root (
@). Use A records only at the root.
4) Cloudflare SSL/TLS & Redirects
- SSL/TLS → Overview: Encryption mode = Full
- Edge Certificates: Always Use HTTPS = ON, Automatic HTTPS Rewrites = ON
- Rules → Redirect Rules (order matters):
- HTTP → HTTPS (place first)
- Request URL:
http://* - Target:
https://{hostname}{uri}(301)
- Request URL:
- Root → WWW (place after)
- If Hostname equals
lchsredcross.org - Target:
https://www.lchsredcross.org/$1(301)
- If Hostname equals
- HTTP → HTTPS (place first)
5) Force GitHub to Re‑check
GitHub → Repo → Settings → Pages
- Click Remove next to the custom domain, Save.
- Re‑enter
www.lchsredcross.org, Save. - This retriggers verification and the HTTPS certificate request.
6) Verify Propagation
Use DNS tools (open in new tab):
- CNAME: https://dnschecker.org/#CNAME/www.lchsredcross.org should show
lawtonchilesredcrossclub.github.io - A record: https://dnschecker.org/#A/lchsredcross.org should show the four GitHub IPs
Propagation can take time globally. If most locations are resolving, GitHub will complete the check soon after.
7) Finalize HTTPS
- When GitHub’s DNS check clears, enable Enforce HTTPS in Settings → Pages.
- Confirm lock icon at https://www.lchsredcross.org
8) If Still Stuck
- Re‑verify there are no records left in Porkbun’s DNS panel.
- In Cloudflare, ensure all records are Proxied (orange cloud).
- Check that DNSSEC is enabled and DS record exists in Porkbun (see DNSSEC Setup).
- Follow the full Verification Checklist (Master).
- If DNS is correct but GitHub won’t verify after a day, open a GitHub Pages support ticket and include screenshots of Cloudflare DNS records.
Quick reference
- CNAME
www→lawtonchilesredcrossclub.github.io - A
@→ 185.199.108.153 / 109.153 / 110.153 / 111.153 - Cloudflare SSL/TLS = Full, Always Use HTTPS = ON, Automatic HTTPS Rewrites = ON
- Redirect order: HTTP→HTTPS first, Root→WWW second