Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
Rather than re-iterate all of its points, I will link Netlify's reasoning in To WWW or Not WWW . It's a very eloquent article. That said, I'll try to summarize in my own words: You need to us...
Answer
#1: Initial revision
by
corporat
·
2021-06-09T21:03:50Z (over 3 years ago)
Rather than re-iterate all of its points, I will link Netlify's reasoning in [To WWW or Not WWW ](https://www.netlify.com/blog/2017/02/28/to-www-or-not-www/). It's a very eloquent article. That said, I'll try to summarize in my own words: * You need to use a CNAME record to direct traffic to their address name for your webapp. Otherwise it can't serve customers content from a local-to-them server address. * You don't want to use a CNAME record on your apex (subdomain-less) domain, because that will prohibit any other records from being registered on your apex domain such as the MX record for email. * It doesn't need to be `www` specifically. That is just a common convention understood by everyone as synonymous with the "root" website.