Personally, I either code so the site doesn't care if "www" is there or not (watch your cookie domain though) or force a redirect to the non-"www" address (part

Personally, I either code so the site doesn't care if "www" is there or not (watch your cookie domain though) or force a redirect to the non-"www" address (particularly when I don't want to purchase 2 SSL certs for a domain). A couple of years a go I would have said to keep the "www" - it's a subdomain that refers specifically to the World Wide Web (or HTTP) address of a site, as opposed to the FTP or email services. Nowadays, I prefer to either drop or ignore the "www" - if you're using an HTTP client to reach my domain, I'm going to go ahead and assume you want the website and not the FTP site. Intelligently named subdomains are good for organization :) So either make both work, or redirect one to the other. It really doesn't matter very much either way.