3 ms·
For example: > Using URLs of the form http://example.com/ http://example.com/ creates a number of problems, and we strongly recommend that you avoid it. http:/
by cbhl 14y ago
For example:
> Using URLs of the form http://example.com/ http://example.com/ creates a number of problems, and we strongly recommend that you avoid it.
http://faq.nearlyfreespeech.net/q/baredomain http://faq.nearlyfreespeech.net/q/baredomain
> zone apex domains (also called bare, naked, or root domains) ... have serious availability implications
https://devcenter.heroku.com/articles/apex-domains https://devcenter.heroku.com/articles/apex-domains
Granted, you don't always have to follow the RFCs...
> the DNS RFC (RFC1033) requires the "zone apex" (sometimes called the "root domain" or "naked domain") to be an "A Record," not a CNAME ... Never one to let a RFC stand in the way of a solution to a real problem, we're happy to announce that CloudFlare allows you to set your zone apex to a CNAME
http://blog.cloudflare.com/zone-apex-naked-domain-root-domain-cname-supp http://blog.cloudflare.com/zone-apex-naked-domain-root-domai...
- eksith 14y ago* = Wildcard A record often held to the same IP as www (and this is fine according to RFC1034) : http://tools.ietf.org/html/rfc1034#section-4.3.3 http://tools.ietf.org/html/rfc1034#section-4.3.3 To be fair, NFS Has had a history of doing things old-school (which is fine for most of their clientele), but the availability implications of Heroku is for something completely different. Also they're a special case with a much more complicated backend.