@svidgenOct 20.2009 — #The resolution of the [B]www[/B] host/subdomain is not automatic or necessarily configured by default when a domain name is registered and pointed at an IP address. A DNS record must be added "manually" to resolve hosts/subdomains. The [B]www[/B] host/subdomain is typically added manually, or may be auto-added by some DNS management [I]software[/I], as an alias to the primary domain.
However, as I understand it, there is nothing inherent [I]to the DNS system[/I] that will point any subdomain to the primary domain without a manually created entry.
Additionally, the web server often needs some configuration to respond properly to the various host/subdomain requests that could come in, and in some cases, apache is/can be configured to ignore requests for domains and subdomains/hosts that are not explicitly allowed.
That all makes sense in my head ... does it make sense in text?
@svidgenNov 06.2009 — #A lot of SEO companies seem to recomend it but I don't beleive it makes any difference. [/QUOTE] I'd be interested to hear the reasoning behind that. The recommendation I've always heard is to avoid redirects, if possible. From what I understand, they create latency for visitors and stop some web crawlers dead in their tracks (not necessarily a bad thing).
Were you given any reason [I]why[/I] one should implement that redirect?
@criterion9Nov 06.2009 — #I was reading up on a similar topic a few months ago and there is a movement to abolish the www prefix altogether since it seems redundant.