|
| 1 | +# DNS Configuration for Website Migration |
| 2 | + |
| 3 | +## Overview |
| 4 | + |
| 5 | +After migrating the website from `reccaller-ai/reccall` to `reccaller-ai/websites`, the DNS configuration may need to be verified or updated. |
| 6 | + |
| 7 | +## Current Setup |
| 8 | + |
| 9 | +- **Custom Domain**: `reccaller.ai` |
| 10 | +- **CNAME File**: Present in `websites` repository |
| 11 | +- **GitHub Organization**: `reccaller-ai` |
| 12 | +- **Old Repository**: `reccaller-ai/reccall` (website archived) |
| 13 | +- **New Repository**: `reccaller-ai/websites` (active website) |
| 14 | + |
| 15 | +## DNS Configuration Requirements |
| 16 | + |
| 17 | +### ✅ Good News: DNS Records Likely Don't Need Changes |
| 18 | + |
| 19 | +Since both repositories are under the same GitHub organization (`reccaller-ai`), and the custom domain (`reccaller.ai`) remains the same, **Cloudflare DNS records typically don't need to be changed**. |
| 20 | + |
| 21 | +### 📋 Verification Steps |
| 22 | + |
| 23 | +#### 1. Check Current Cloudflare DNS Records |
| 24 | + |
| 25 | +In Cloudflare dashboard, verify your DNS records for `reccaller.ai`: |
| 26 | + |
| 27 | +**For Apex Domain (reccaller.ai):** |
| 28 | +- **Type**: `A` records |
| 29 | +- **IP Addresses**: Should point to GitHub Pages IPs: |
| 30 | + - `185.199.108.153` |
| 31 | + - `185.199.109.153` |
| 32 | + - `185.199.110.153` |
| 33 | + - `185.199.111.153` |
| 34 | +- **Proxy Status**: Should be "DNS only" (gray cloud) ☁️ |
| 35 | + |
| 36 | +**For WWW Subdomain (www.reccaller.ai):** |
| 37 | +- **Type**: `CNAME` |
| 38 | +- **Name**: `www` |
| 39 | +- **Target**: `reccaller-ai.github.io` (or your GitHub Pages URL) |
| 40 | +- **Proxy Status**: Should be "DNS only" (gray cloud) ☁️ |
| 41 | + |
| 42 | +#### 2. Configure GitHub Pages Custom Domain |
| 43 | + |
| 44 | +**In the new repository** (`reccaller-ai/websites`): |
| 45 | + |
| 46 | +1. Go to: https://github.com/reccaller-ai/websites/settings/pages |
| 47 | +2. Under **"Custom domain"**, enter: `reccaller.ai` |
| 48 | +3. Click **"Save"** |
| 49 | +4. GitHub will verify the DNS configuration |
| 50 | +5. Enable **"Enforce HTTPS"** (recommended) |
| 51 | + |
| 52 | +#### 3. Verify DNS Propagation |
| 53 | + |
| 54 | +After updating GitHub Pages settings: |
| 55 | + |
| 56 | +```bash |
| 57 | +# Check DNS records |
| 58 | +dig reccaller.ai +short |
| 59 | + |
| 60 | +# Check GitHub Pages verification |
| 61 | +# GitHub will show verification status in repository settings |
| 62 | +``` |
| 63 | + |
| 64 | +### ⚠️ When DNS Changes ARE Needed |
| 65 | + |
| 66 | +DNS changes are only needed if: |
| 67 | + |
| 68 | +1. **Different GitHub Account/Organization**: If you moved to a different GitHub account/org, the GitHub Pages URL changes, and DNS needs updating. |
| 69 | + |
| 70 | +2. **Different Domain**: If you're using a different domain name. |
| 71 | + |
| 72 | +3. **Previous DNS Pointed to Specific Repo**: If your DNS was configured to point to a specific repository path (unlikely for apex domains). |
| 73 | + |
| 74 | +### ✅ What We Already Have Correct |
| 75 | + |
| 76 | +1. ✅ `CNAME` file exists in `websites` repository with `reccaller.ai` |
| 77 | +2. ✅ Same GitHub organization (`reccaller-ai`) |
| 78 | +3. ✅ Same custom domain (`reccaller.ai`) |
| 79 | + |
| 80 | +### 📝 Action Items |
| 81 | + |
| 82 | +1. **In GitHub** (websites repository): |
| 83 | + - ✅ CNAME file already present |
| 84 | + - ⚠️ **REQUIRED**: Enable GitHub Pages with custom domain in repository settings |
| 85 | + - ⚠️ **REQUIRED**: Configure custom domain in Settings → Pages |
| 86 | + |
| 87 | +2. **In Cloudflare**: |
| 88 | + - ✅ **Verify** DNS records are correct (likely no changes needed) |
| 89 | + - ✅ **Confirm** A records point to GitHub Pages IPs |
| 90 | + - ✅ **Confirm** Proxy status is "DNS only" (not proxied) |
| 91 | + |
| 92 | +3. **Verification**: |
| 93 | + - Wait for DNS propagation (5-60 minutes) |
| 94 | + - Test `reccaller.ai` in browser |
| 95 | + - Verify HTTPS certificate is issued |
| 96 | + |
| 97 | +## Summary |
| 98 | + |
| 99 | +**Most Likely Scenario**: No Cloudflare DNS changes needed. |
| 100 | + |
| 101 | +**Why**: Same organization, same domain, just different repository. GitHub Pages handles the routing based on the `CNAME` file and repository settings. |
| 102 | + |
| 103 | +**Only Action Required**: |
| 104 | +- Enable GitHub Pages in `reccaller-ai/websites` repository settings |
| 105 | +- Configure custom domain in GitHub Pages settings |
| 106 | +- Verify DNS records in Cloudflare (should already be correct) |
| 107 | + |
| 108 | +## Troubleshooting |
| 109 | + |
| 110 | +If the site doesn't work after migration: |
| 111 | + |
| 112 | +1. Check GitHub Pages deployment status |
| 113 | +2. Verify CNAME file in repository |
| 114 | +3. Check DNS records in Cloudflare match GitHub Pages requirements |
| 115 | +4. Wait for DNS propagation (can take up to 48 hours, usually 5-60 minutes) |
| 116 | +5. Check GitHub Pages domain verification status |
| 117 | + |
| 118 | +## Reference Links |
| 119 | + |
| 120 | +- GitHub Pages Custom Domain Docs: https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site |
| 121 | +- Cloudflare DNS Settings: https://dash.cloudflare.com |
| 122 | +- GitHub Pages Settings: https://github.com/reccaller-ai/websites/settings/pages |
| 123 | + |
0 commit comments