81–90 of 93 posts
I think that this can vary quite a bit. My simple GitHub page loads in roughly 1 second. I don't think it's ever taken as long as 5 seconds. The linked site loads in less than half a second, but it costs $5 a month just for a simple page.
Earlier quoted context omitted.
I didn't see such a note, but I'm not sure it would be true, either. DNSimple doesn't actually implement a new DNS record type, it simply puts a TXT record on your domain that says "ALIAS for some.fqdn", and presumably it causes their DNS servers to do a recursive lookup for you (to whatever's in the TXT record) when you try and look at the A record for the naked domain. From github's DDoS prevention's point of view…
No, the result is not the same. When you look up the records for the .github.io you get a different set of records than the singular IP address they tell you to add if you want to use the apex domain! So from Github's DDoS prevention's point of view, the result is different.
What's to stop users from doing their own lookup, and setting their A record to what the result is?
In other words, they make it really easy to make your site fast but still catch users that didn't bother typing 'www.'
https://help.github.com/articles/setting-up-a-custom-domain-...
Cole with Brace here ( http://brace.io ). We recommend redirecting the apex domain to a "www" subdomain. Note that even using apex CNAME records (Alias records) are still a new idea, and depending on the implementation may reduce reliability or performance. ( https://iwantmyname.com/blog/2014/01/why-alias-type-records-... ) Here are a few resources from our blog that explain the www redirect approach: - http://blog.b…
https://iwantmyname.com/blog/2014/05/alias-type-dns-records-...
Hope it's helpful!
Earlier quoted context omitted.
No, the result is not the same. When you look up the records for the .github.io you get a different set of records than the singular IP address they tell you to add if you want to use the apex domain! So from Github's DDoS prevention's point of view, the result is different.
So the answer to the issue is that the IP github tells you to use is the slow one? That sounds strange. What's to stop users from doing their own lookup, and setting their A record to what the result is?
Hey folks, Jesse from GitHub Ops here. First off, if you use a DNS provider that has support for a ALIAS records or something similar, pointing your apex domain to .github.io will ensure your GitHub Pages site is served by our CDN without these redirects. I wish we could provide better service for folks without a DNS provider that supports ALIAS domains in the face of the constant barrage of DDoS attacks we've seen a…
I think it's fantastic that you provide apex support for everyone even though it must be exponentially harder to do that just providing CNAMEs, but if you're upfront about the limitations the only people who are going to complain are the type of people you don't want to be listening to anyway.
[0] I mean that in the sense that they'll comprehend the explanation, not that they'll grok it inherently.
If you’re having trouble with a root domain on Github pages you may want to check out the Hosting product we (Firebase) just announced. It handles naked domains by having your root A record point to an Anycast IP that serves content from a global CDN. It’s lightning fast. We also support SSL (full SSL, not just SNI) and do the cert provisioning automatically for you. Check it out: https://www.firebase.com/blog/2014-0…
I use a subdomain of that main domain as the User Pages site.
How should DNS be setup and how should the CNAME files on GitHub read?
As an example, the domain on the left should load the site normally hosted from the location on the right:
example.com -> username.github.io/blog
io.example.com -> username.github.io
Is this possible?
Hey folks, Jesse from GitHub Ops here. First off, if you use a DNS provider that has support for a ALIAS records or something similar, pointing your apex domain to .github.io will ensure your GitHub Pages site is served by our CDN without these redirects. I wish we could provide better service for folks without a DNS provider that supports ALIAS domains in the face of the constant barrage of DDoS attacks we've seen a…
(I work on DNS things and am curious about what exactly a CDNs needs are.)