Hot answers tagged github
You answered your own question. They said to set CNAME or A record. As for the Nameservers, unless GitHub says otherwise, you are going to ask what the A Record or CNAME should be set on your domain name. Then, if you don't know how, ask your Domain Register about setting the CAME or A Record to what it needs to be for your domain name.
If the DNS has started to propagate, you may be facing caching on your computer or ISP's DNS server. I'd wait for a bit, or try either: temporarily using a different DNS provider, e.g. OpenDNS or Google Public DNS (you may need to restart your browser or OS) checking from a computer using a different ISP/DNS server Good luck.
As covered here, GitHub Pages is served with Nginx and automatically gzip's content. You can confirm gzip compression for your site by checking the HTTP headers with online tools like this one. Enter the URL to a webpage or resource, and type in gzip under "Accept-Encoding" to indicate that the HTTP client (i.e., the online testing tool in this case) ...
Since it based on rendering plain files from a git repository, I don't think you can use dynamic information. The goals of Github Pages is to show a static site easily from an open source project. You can still contact them and I think you have a dedicated support if you use Github Enterprise.
Do I use a CNAME for www only then, with no A record at all? You would need to use a CNAME for the www.example.com subdomain, and an ALIAS record for your root domain example.com (aka., "apex domain"). As indicated in the help document you provided on Setting up a custom domain with Pages: Some DNS providers (like DNSimple) allow you to use an ...
Here is the relevant help page: https://help.github.com/articles/user-organization-and-project-pages They have two types of pages: User/Organization Pages and Project Pages Based on this, they are not limiting the use of Github Pages to just software projects. They allow pages for users and organizations.
GitHub allows you to create a custom 404 page but there is a caveat. The 404 will be displayed only if you use a custom domain or for user pages. Custom 404s only work when they are served from the root of a Pages domain, for example a project using a custom domain or a user pages repository. A custom 404 page on project pages that are not using a custom ...
According to the GitHub documentation on custom 404s you are out of luck: Custom 404s only work when they are served from the root of a Pages domain, for example a project using a custom domain or a user pages repository. It looks like sub-folders are not supported. Only the root folder.
I eventually gave in and solved this with a Apache config redirect (although I wanted to do it with pure DNS it looks like this is not possible...) <VirtualHost *:80> DocumentRoot /www/html/firstdomain.com ServerName firstdomain.com RedirectMatch 301 ^(.*)$ http://seconddomain.com$1 ErrorLog logs/firstdomain.com-error_log TransferLog ...
Only top voted, non community-wiki answers of a minimum length are eligible