custom domain without redirect

[loglot]

Select Topic Area

Question

Body

i have a domain purchased via godaddy, and i have a website that i am running via github pages, i have been able to get it working with the domain, however, when i try to go to the github.io link it just redirects to my domain. i want it to be able to be accessible from both links, without one redirecting to another

[behdad088]

Hi @loglot
To achieve your goal of having your GitHub Pages site accessible from both the GitHub Pages URL and your custom domain without redirection, you can adjust a few settings. Here's how you can do it:

1. GitHub Pages CNAME Removal

• If you have a custom domain set up on GitHub Pages, GitHub creates a CNAME file in your repository's root or docs directory (wherever your GitHub Pages site is hosted). This file forces a redirect from yourusername.github.io/reponame to your custom domain.
• To stop the redirection:
  • Go to your GitHub repository.
  • Look for the CNAME file in the repository root (or in the branch you're using for GitHub Pages, often main or gh-pages).
  • Delete the CNAME file if it's present.

2. DNS Configuration

• Ensure that your DNS settings in GoDaddy are correctly pointing to GitHub Pages.
  • Go to GoDaddy's DNS management.
  • Set up the necessary A records and CNAME records as per GitHub Pages documentation. Typically:
    • A records should point to the GitHub Pages IP addresses:

      185.199.108.153
      185.199.109.153
      185.199.110.153
      185.199.111.153
      

    • A CNAME record pointing your custom domain (e.g., www.yourdomain.com) to yourusername.github.io.
• Important: You do not need to set any redirection within GoDaddy's DNS settings.

3. Configure Custom Domain on GitHub

• Even though you removed the CNAME file in Step 1, you still need to set up your custom domain in GitHub.
  • Go to your GitHub repository settings.
  • Under the "Pages" section, in the "Custom domain" field, enter your custom domain (e.g., www.yourdomain.com).
  • Uncheck the "Enforce HTTPS" option if you want to avoid the redirect (although HTTPS is recommended for security, this could cause GitHub Pages to prefer the custom domain for requests).

4. Test

• Visit both:
  • yourusername.github.io/reponame
  • www.yourdomain.com
• Both URLs should now serve the same site without any redirection.

By removing the CNAME file, you prevent GitHub Pages from redirecting visitors automatically, allowing both the GitHub Pages URL and your custom domain to coexist.

[loglot]

Sounds good! I'll try it soon

[loglot]

whenever i add the domain, a CNAME file gets added, no exceptions, and when i delete the CNAME file, it no longer pushes the page to the domain, any help?

[loglot]

also, the custom domain works whenever the CNAME file exists, so i think the dns on godaddy's end is fine

[behdad088]

So, the issue with GitHub Pages is that when you add a custom domain, it automatically creates a CNAME file in your repo. That file is what makes your custom domain work, but it also forces the GitHub Pages URL (like yourusername.github.io/reponame) to redirect to the custom domain.

Basically, GitHub won’t let you use both URLs without one redirecting to the other if the CNAME file is there. And if you delete the CNAME file to stop the redirect, your custom domain breaks. 🙃

Workarounds:

1. Use a Subdomain: Instead of using your full domain (like www.yourdomain.com), you could use something like pages.yourdomain.com. This way, both the GitHub Pages URL (yourusername.github.io/reponame) and the subdomain will work without any redirects. It's super easy to set up, just update your DNS in GoDaddy to point the subdomain to GitHub.

2. Two Repos: You could have two separate GitHub repos—one for the yourusername.github.io/reponame and another one for your custom domain. Both will have the same content, but they’ll be hosted separately. You’ll just need to sync them whenever you make updates.

3. External Hosting: If you’re okay with using something like Netlify or Vercel, you could keep the GitHub Pages URL active and host the custom domain on one of those services. This way, both URLs will work, and there won’t be any redirects between them.

4. Advanced Option – Proxy: If you’re feeling fancy, you could set up a proxy server (like with Nginx) that serves both URLs without the redirect. But this involves a bit more setup, so it’s probably overkill unless you’re into server stuff.

Honestly, the subdomain option is probably the easiest way to go. It keeps everything simple and still gives you access to both the GitHub Pages URL and your custom domain without the redirect issue. Let me know if you want to try it out or need help setting it up!

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬