WWW is Deprecated

I’ve always hated the www. subdomain.

Now I have the solution: http://no-www.org/.

[Hey, this is short, but I have an acceptance test report to re-write this afternoon, and it’s not mine.]

4 comments

  1. I have another nitpick here. no-www.org’s comparison of web servers to mail servers isn’t quite an apples-to-apples comparison.

    When you type the URL “http://host.domain.com/”, “host.domain.com” is expected to be a fully-qualified domain name. In other words, it resolves to a specific IP address through DNS. Your web browser looks up that IP address and makes a direct connection to the computer at that IP address.

    Mail, however, is a special case. When you send an email to “user@domain.com”, “domain.com” is NOT assumed to be a FQDN. The first step is for your mail server to look up the MX record for “domain.com”, which returns the FQDN of the computer designated to handle mail for “domain.com”. THEN, that FQDN is translated to the IP address, which is used by the mail server to make the connection. The FQDN could very well be “mail.domain.com”.

    no-www.org’s argument is that since you can send email to “user@domain.com”, you should be able to type “http://domain.com” in your web browser. Well, what if domain.com maintains different physical servers for web (www.domain.com) and mail (mail.domain.com) with different IP addresses, and it wants both to be visible to the outside world? That was the original reason for what no-www.org is calling the “subdomain”. It’s not a subdomain. It’s a hostname.

    I admit that this is much rarer these days than it used to be. Creative use of DNS entries, firewalls with port forwarding, and other cool stuff can often eliminate the need for the “www” (or any other host name) in most cases. So, I don’t fundamentally disagree with their point, but their example isn’t as technically sound as they seem to think it is.

Comments are closed.