4 ms·
With "www". That makes it a lot easier to add in CDN support, DNS based load balancers, and a ton of other tools down the line. Why? Because you need your doma
by tedivm 13y ago
With "www". That makes it a lot easier to add in CDN support, DNS based load balancers, and a ton of other tools down the line.
Why? Because you need your domain root to have all sorts of other stuff in it- MX records, SPF keys, and various other things. A lot of CDNs and DNS based tools work really well by utilizing CNAMEs, which you can't do on the root. Putting your website on "www" keeps is as a separate isolated service and makes adding those services easier down the line.
- igor47 13y agoThis. Don't use your zone apex name as your main site. You will regret it. If visitors come to the non-www version of the site send them a 301 redirect.
- unclebucknasty 13y agoI'm not sure I understand this advice. The domain root can still have the CNAME, TXT, SPF, MX records, etc. while pointing the zone root to the website's IP. These are all just different record types within the zone, right?
- dhoulb 13y agoI think he's saying, if in the future you want to route web traffic through a CDN, using a CNAME, instead of directly at a specific server, using an A record, you're going to struggle if you're using the root name, as you can't have root CNAMEs. Damn good reason too! I can't think of a good way round it. Do people like CloudFlare configure using CNAMEs? If they do, this strongly weights my decision, (along with the 'non expert users like www.' argument - though I think as long as you use a .com you're probably okay there).
- tedivm 13y agoCloudFlare actually hosts the DNS of the domains using them, except for people who pay for the premium accounts. Then they rely on CNAMEs. You hit what I was saying spot on. It's not just a matter of CDNs either, there are a lot of services where using CNAMEs become important.
- lingben 13y agowhat if you don't use CNAMEs? A records are much better imho