In this quick guide, I’ll show you how to setup your custom domain in GH Pages, configure the DNS records, and establish the https protocol for a safer aspect of our website.
Table of content
Introduction
Recently, I have found myself surfing the web trying to find out how to set up my new domain. I’ve been using Github Pages for a while now, and I considered buying a domain to professionalize my blog. For me, I chose Hostinger because of its inexpensive price and its incredible upgrade potential. For example, you can obtain a professional email with your website name in it, for less than a monthly coffee.
Buying the domain
First of all, we need our fresh domain. If you already have one, you can skip this step. As I said, before, I recommend Hostinger, but there are plenty of pages where you can get one almost for free. We’ll need to check that our domain is available, and then we will proceed to buy it.
As you can see, prices are quite attractive.
Getting Github ready
First of all, we will need to access the GH Pahes configuration file of our repo.
Mine is already set up (otherwise, you wouldn’t be able to see this). We will fill the custom domain box with… our custom domain. One could think that, if it was this easy, anyone could copy each other’s domains. That’s why DNS records exist. These are a series of instructions that tell our server how to manage petitions to our website, and we must configure them to our domain to work.
Configuring DNS records
With this objective, we have to sign in to Hostinger (or your selected provider), and go to manage domain:
Now, we have to click in DNS / Nameservers (Or its equivalent)
Now we have to add a DNS record per Github Pages IP. We can do this by selecting type “A”, name “@” and pointing to each of these IPs (you have to add 4 DNS records):
185.199.108.153
185.199.109.153
185.199.110.153
185.199.111.153
Once you have added all of them, we may have to wait a while to see our domain functioning, but in most cases, Hostinger does his job quickly. If we want, we can check in our command line if it is alright, using the next command:
dig yourweb +nostats +nocomments +nocmd
replacing “yourweb” with your website.
If the output look like this (if you want it to look this good, check my tutorial), it will be ready to go!
Getting your Free SSL certificate
Last, but not least, we have to check a few more todos to our website to look safe, for both search engines and our visitors. The standard of security these days is SSL, but Github offers us a free TLS Certificate, an improved version of SSL. Sounds good, right?
We have to add a new DNS record, so access the same page as before. Choose: type “CNAME”, name “www” and points to “yourgithubuser.github.io”, changing “yourgithubuser” for, forgive the redundancy, your GitHub user. Click add, and the last thing you have to do is go to your repo Pages configuration and check the “Enforce HTTPS” checkbox. Now wait a few minutes (it shouldn’t take long), and your certificate will come into effect.
Conclusion
I hope that you found this article helpful. I had to scroll through many docs to write it, and I wanted to save the effort for you. I will be delighted to read your comments if you have any questions. If you want to support me, please share with anyone who may find this of help. It means a lot!