4 ms·

I wrote about this over 10 years ago and it mostly still holds true today... See: https://wade.be/yes-www/ https://wade.be/yes-www/ I still think the best arg

I wrote about this over 10 years ago and it mostly still holds true today... See: https://wade.be/yes-www/ https://wade.be/yes-www/ I still think the best argument for keeping www is from Heroku: "Root domains are aesthetically pleasing, but the nature of DNS prevents them from being a robust solution for web apps. Root domains don't allow CNAMEs, which requires hardcoding IP addresses, which in turn prevents flexibility on updates to IPs which may need to change over time to handle new load or divert denial-of-service attacks."" See: https://web.archive.org/web/20110628072339/http://status.heroku.com:80/incident/156 https://web.archive.org/web/20110628072339/http://status.her... Like most things in technology, if Amazon, Facebook and Google are all doing it, it's probably for good reason...

sneak 8y ago
These days almost all dns providers support dns-server-resolved CNAMEs (ANAMEs as they are known). I don’t think this is really much of an issue anymore.
- ericpauley 8y ago
  AWS Route 53 doesn't support this for external CNAMEs, just aliases for amazon resources.
paulddraper 8y ago
But not Twitter?
tln 8y ago
I don't think Amazon Facebook and Google would have any technical trouble using an alias... "www" is all about conforming to expectations
RKearney 8y ago
> which requires hardcoding IP addresses That statement couldn't be more wrong. It's absolutely possible to programmatically update DNS records. Set the TTL low (which you would be anyway for the CNAME records) and change them as you see fit.
DonHopkins 8y ago
There's a good reason for wage collusion??!
- lifeformed 8y ago
  Well, yes. "Good" as in "it works well".
deleted 8y ago
[deleted]