Ask Why does my custom domain still redirect to GitHub page?

[Brajet]

Hi,

I initially have my website at Github Pages but I'm moving it to render.com or other platform.

Configured on eng render.com (may verification on ng domain).

2. ⁠ Deleted on din ang DNS sa Github Pages

3. ⁠ Deleted on din ang CNAME sa Github Repo

4. ⁠ Configured on din ang namecheap.com DNS ko to redirect sa render.com

Despite all this, it still redirect to a Github page.

Am I missing something?

 

[Anthony Joshua]

It's likely a caching or propagation delay problem. DNS updates aren't instant, especially if GitHub's records were live before. Try using tools like "whatsmydns.net" to see if your domain is still pointing to GitHub IPs. If yes, just wait for it to update everywhere. Also, confirm your browser cache isn't holding the old redirect, it can trick you into thinking it's not fixed yet.

 

[Felix😎]

Hi,

I initially have my website at Github Pages but I'm moving it to render.com or other platform.

Configured on eng render.com (may verification on ng domain).

2. ⁠ Deleted on din ang DNS sa Github Pages

3. ⁠ Deleted on din ang CNAME sa Github Repo

4. ⁠ Configured on din ang namecheap.com DNS ko to redirect sa render.com

Despite all this, it still redirect to a Github page.

Am I missing something?

First, make sure that the DNS settings on Namecheap have fully propagated and are correctly pointing to your new Render.com site. Sometimes it can take a little while for DNS changes to update across the internet.

Also, double-check that you've fully removed the CNAME record from your Github repo. If that CNAME is still there, it could be causing the redirect to continue going to the old Github Pages site.

Another thing to verify is that you don't have any caching or browser extensions that might be causing the old redirect to persist. Try accessing the site from a different device or in incognito mode to see if that helps.

If you've confirmed all those steps, my best advice would be to reach out to Render.com support. They should be able to help you troubleshoot any remaining issues with the domain redirection.

 

[Dean101]

Most times it's just DNS not pointing the right way or it hasn't fully updated across the internet yet. That can take a few hours or even up to a couple of days. Another common issue is GitHub Pages not being set properly in your repo settings, or your custom domain not being added there correctly. Also, if you only set up either the "www" version or the bare domain and not both, one of them might still send you to GitHub's default page. Sometimes it's also just your browser holding onto old info, so clearing cache or trying another device can help.