"Then, redirect the root domain to the www subdomain using a DNS CNAME record."
But you aren't meant to CNAME the root zone, in case you have other records at that level (MX, NS, SOA etc.)?
GitHub Pages with a custom root domain is slow
11–20 of 93 posts
Re: GitHub Pages with a custom root domain is slow
#12This article links to [1] as an explanation for the delay, but that article says at the top that Github has since updated their configuration instructions to help people avoid the issue.
[1] http://helloanselm.com/2014/github-pages-redirect-performanc...
Re: GitHub Pages with a custom root domain is slow
#13Is 5s really such a problem? I don't think I'd bail out of a website because it took 5s to load, unless it was something I didn't particularly want to see anyway. Which I guess might be why people didn't stick around for the tests from which the 35% number is drawn.
Re: GitHub Pages with a custom root domain is slow
#14Sounds like if you use Github Pages with a zone apex URL, you're losing out on their CDN.
Re: GitHub Pages with a custom root domain is slow
#15>The short solution is, instead of using yourdomain.com, use www.yourdomain.com. Then, redirect the root domain to the www subdomain using a DNS CNAME record.
The root can't be a CNAME because no other record with the same name aside of a CNAME can exist. Your domain root also has one SOA and two NS records (and probably one more more MX records if you want to receive mail)
See RFC 1912 (Section 2.4)
Re: GitHub Pages with a custom root domain is slow
#16I don't believe the lose.
On a GitHub page are programming specific solutions for a problem a developer has.
When somebody search for a problem or find a link to a GitHub Project, he/she will visit the page.
All others don't have an urgent problem to solve, so you loose only users, that not need your solution. Can live with it. ;-)
Re: GitHub Pages with a custom root domain is slow
#17Is 5s really such a problem? I don't think I'd bail out of a website because it took 5s to load, unless it was something I didn't particularly want to see anyway. Which I guess might be why people didn't stick around for the tests from which the 35% number is drawn.
[deleted]
Re: GitHub Pages with a custom root domain is slow
#18Is 5s really such a problem? I don't think I'd bail out of a website because it took 5s to load, unless it was something I didn't particularly want to see anyway. Which I guess might be why people didn't stick around for the tests from which the 35% number is drawn.
[deleted]
Re: GitHub Pages with a custom root domain is slow
#19>The short solution is, instead of using yourdomain.com, use www.yourdomain.com. Then, redirect the root domain to the www subdomain using a DNS CNAME record. The root can't be a CNAME because no other record with the same name aside of a CNAME can exist. Your domain root also has one SOA and two NS records (and probably one more more MX records if you want to receive mail) See RFC 1912 (Section 2.4)
Came here to say the same thing. It can play hell with your email if you do manage to put a CNAME on the root [0].
[0] http://joshstrange.com/why-its-a-bad-idea-to-put-a-cname-rec...
Re: GitHub Pages with a custom root domain is slow
#20>The short solution is, instead of using yourdomain.com, use www.yourdomain.com. Then, redirect the root domain to the www subdomain using a DNS CNAME record. The root can't be a CNAME because no other record with the same name aside of a CNAME can exist. Your domain root also has one SOA and two NS records (and probably one more more MX records if you want to receive mail) See RFC 1912 (Section 2.4)
Came here to say the same thing. It can play hell with your email if you do manage to put a CNAME on the root [0]. [0] http://joshstrange.com/why-its-a-bad-idea-to-put-a-cname-rec...
[deleted]