🌐 DNS Configuration Guide - WordPress to GitHub Pages Migration

Complete guide for migrating thebeier.com from WordPress to GitHub Pages

Current Status:

✅ CNAME file updated to: thebeier.com
✅ Changes committed and pushed to GitHub
⏳ Awaiting DNS configuration at your domain registrar

📋 Migration Checklist

Backup WordPress site and database
Export all blog posts from WordPress
Update CNAME file in GitHub repository (COMPLETED ✅)
Configure DNS records at domain registrar (SEE BELOW)
Wait for DNS propagation (24-48 hours)
Verify site is accessible at thebeier.com
Enable HTTPS in GitHub Pages settings
Update all hardcoded URLs in content
Set up redirects from old WordPress URLs (if needed)
Update RSS feed URLs in your profiles/links
Test all functionality on new domain
Decommission old WordPress site

🔧 DNS Configuration

⚠️ Important: These changes must be made at your domain registrar (where you purchased thebeier.com). Common registrars include GoDaddy, Namecheap, Google Domains, Cloudflare, etc.

1Option A: Using A Records (Recommended)

Add the following A records for the root domain (@):

A Record #1 Type: A | Name: @ | Value: 185.199.108.153 | TTL: 3600

A Record #2 Type: A | Name: @ | Value: 185.199.109.153 | TTL: 3600

A Record #3 Type: A | Name: @ | Value: 185.199.110.153 | TTL: 3600

A Record #4 Type: A | Name: @ | Value: 185.199.111.153 | TTL: 3600

2Add CNAME for www subdomain

CNAME Record

Type: CNAME | Name: www | Value: thiagogbeier.github.io | TTL:
						3600

What this does:

thebeier.com → Points to GitHub Pages
www.thebeier.com → Redirects to thebeier.com

3Remove Old DNS Records

⚠️ Before migrating: Remove or disable any existing A records or CNAME records pointing to your WordPress hosting. Otherwise, DNS conflicts may occur.

⏱️ Timeline & Propagation

Immediate (Within 5 minutes)

GitHub recognizes the CNAME file change
Site accessible at: https://thiagogbeier.github.io

1-4 Hours (DNS Propagation Begins)

DNS records start propagating globally
Some locations will see the new site
Others will still see WordPress

24-48 Hours (Full Propagation)

All DNS servers worldwide updated
thebeier.com reliably points to GitHub Pages
HTTPS certificate should be available

🔐 Enable HTTPS (After DNS Propagation)

⏳ Wait for DNS: You cannot enable HTTPS until DNS propagation is complete. GitHub needs to verify domain ownership first.

1Go to Repository Settings

Navigate to: Repository → Settings → Pages

2Verify Custom Domain

You should see: Custom domain: thebeier.com
Status should show: ✅ DNS check successful

3Check "Enforce HTTPS"

Enable the "Enforce HTTPS" checkbox
GitHub will automatically provision a Let's Encrypt SSL certificate
This may take a few minutes

✅ Once enabled: All traffic will be automatically redirected from http:// to https://

🧪 Testing DNS Propagation

Check DNS Records

					# Windows PowerShell nslookup thebeier.com # Should show GitHub IPs
						(185.199.108-111.153) # macOS/Linux dig thebeier.com # Should show A
						records pointing to GitHub
				

Online Tools

WhatsMyDNS.net - Check propagation worldwide
DNSChecker.org - Verify DNS records globally
MXToolbox - Comprehensive DNS diagnostics

🔄 Post-Migration Tasks

Update URL References

Files that may contain hardcoded URLs:

rss.html - Update RSS feed documentation URLs
blog/posts/*.html - Check internal links in blog posts
index.html - Update any absolute URLs in main page
README.md - Update documentation links

Update External References

Social media profiles (LinkedIn, Twitter, etc.)
RSS feed subscribers (notify if necessary)
Email signatures
Business cards or marketing materials
Any backlinks or guest posts

New RSS Feed URL

Updated RSS Feed: https://thebeier.com/blog/feed.xml

RSS Note: If users have subscribed to your old RSS feed, consider keeping a redirect or notification about the new URL. Most RSS readers will automatically follow redirects.

❗ Troubleshooting

Problem: "Domain's DNS record could not be retrieved"

DNS records not configured correctly at registrar
DNS propagation still in progress (wait longer)
Verify A records point to all 4 GitHub IPs

Problem: "Certificate Not Yet Created"

DNS must fully propagate first (wait 24-48 hours)
Try unchecking and re-checking "Enforce HTTPS"
Verify custom domain shows as verified in GitHub Settings

Problem: "Site Not Secure" Warning

HTTPS not yet enabled in GitHub Pages settings
SSL certificate still provisioning (wait a few minutes)
Clear browser cache and try incognito mode

Problem: Mix of Old and New Site

This is normal during DNS propagation
Different DNS servers return different results
Wait for full propagation (24-48 hours)
Test from different networks or use VPN

📞 Support Resources

✅ Next Steps Summary

Configure DNS records at your domain registrar
Wait 24-48 hours for DNS propagation
Enable HTTPS in GitHub Pages settings
Update all URL references in your content
Test thoroughly before decommissioning WordPress