🌍 DNS Propagation Guide

This page explains what DNS propagation is, why it causes delays, how to check it, and what to do if the domain seems stuck at “DNS Check in Progress.”

---

What is DNS Propagation?

• When DNS records are updated (like pointing to GitHub Pages), the changes don’t apply instantly worldwide.
• Each internet provider caches DNS results, and it can take a few minutes up to 24–48 hours to refresh everywhere.
• During this time, some people may reach the new site while others still see errors or the old site.

---

Why It Matters

• GitHub Pages won’t issue HTTPS until DNS records are recognized worldwide.
• Seeing ❌ on DNSChecker doesn’t always mean something is broken — it often just means propagation is still happening.

---

How to Check DNS Propagation

1. Go to DNSChecker.org.
2. Test two records:
   • CNAME (www.lchsredcross.org) → should point to lawtonchilesredcrossclub.github.io
   • A Record (lchsredcross.org) → should point to GitHub IPs:
     • 185.199.108.153
     • 185.199.109.153
     • 185.199.110.153
     • 185.199.111.153
3. Look at the map:
   • ✅ = updated and correct
   • ❌ = still using old/broken data

---

What to Do if It Seems Stuck

• Normal waiting: If you see a mix of ✅ and ❌, give it more time (can take up to 24 hours).
• Possible misconfig: If after 24 hours most are ❌, check:
  • Porkbun → make sure only Cloudflare nameservers are listed.
  • Cloudflare → make sure only the correct CNAME and A records exist.
• GitHub Pages reset: If DNS is correct but GitHub still says “DNS Check in Progress,” remove and re-add the custom domain in Settings → Pages.

---

When Propagation is Complete

• Both www.lchsredcross.org and lchsredcross.org show mostly ✅ results worldwide.
• GitHub’s DNS check passes and Enforce HTTPS becomes available.
• You can then enable HTTPS for the site in GitHub Pages.

---

✅ Summary: DNS propagation delays are normal. Wait, verify with DNSChecker, and only reconfigure if results stay ❌ after 24 hours.