Here is DNS Settings For Custom Domain For GitHub To Point Your Naked Custom Domain Towards GitHub’s Nodes From Rackspace DNS or CloudFlare. This also can be used to solve the naked domain pointing issues for Free PaaS Hosting like RedHat OpenShift or Heroku Cloud. As there will be an IP address, either you can use the GitHub Pages to Host Content or tweak to point towards IP-less PaaS. Do not abuse it.
DNS Settings For Custom Domain For GitHub
Forget about www part! It is alias. Naked Domain. GitHub is also hosted on Rackspace! They have two IP address for the front end nodes :
|
1 2 |
192.30.252.153 192.30.252.154 |
What we do in case of own server – the Cloud DNS point towards the server and name server point towards Rackspace. We are assuming that you have a Rackspace Cloud Account and running servers. For project website, you’ll not pay! So in case you are using Rackspace’s internal Domain Name Service (Click and Name, historically for Cloud Sites), point towards Rackspace :
---
|
1 2 3 4 |
dns1.stabletransit.com dns2.staletrasit.com ns.rackspace.com ns2.rackspace.com |
and from Cloud DNS, you’ll set the A record. Otherwise, how the domain name will get resolved?
This is my GitHub users page’s url – http://abhishekghosh.github.io
If I run dig abhishekghosh.github.io, I will get an IP address, right? It is a CNAME mapped to github.map.fastly.net with the IP 103.245.222.133. There are complicated things on Rackspace, so that 192.30.252.xxx set actually works.
DNS Settings For Custom Domain For GitHub : CNAME File
Naked Domain and CNAME is strict NO NO. This is my GitHub Page’s repo :
|
1 |
https://github.com/AbhishekGhosh/AbhishekGhosh.github.io |
In your repository’s right sidebar, there is Settings. Under “GitHub Pages”, you should see your GitHub custom domain name ( http://abhishekghosh.github.io for me ). Next, go to the GitHub repo, navigate to your Pages repository. For User and Organization Pages sites, the Pages branch will be master and for Project Pages sites, the Pages branch will be gh-pages. What Will be? Will be is creation of a CNAME file. Inside that CNAME file write the naked domain name or the subdomain name.
Quite obviously, if you are using a subdomain like git.thecustomizewindows.com, A name record is not required, CNAME will work fine. But, you have to arrange the domain name resolution if there is no server against thecustomizewindows.com ? Thats why naked domain name. Github dislikes naked domain pointing. You can Rackspace support for help (obviously oif you are a Rackspace client and using Cloud DNS).
If you are not a Rackspace client, then you’ll use Cloudflare. The A will be @ with IP and if CNAME needed, add it. Rackspace-Rackspace is internal, its easy. Outside Cloud DNS, a bit experimentation with IP might be needed. That CNAME file is your virtualhost file!
If nothing works, then use a 3-5 USD shared hosting to get an IP to resolve. Keep in mind, this is strictly not for making your WordPress converted to Jekyll and hosted on GitHub.
Tagged With github pages Domains DNS record could not be retrieved , github dns settings