Harlan Messinger wrote:
>>
I was under the impression that the "www" is necessary and that if
people don't type it in browsers just put it in.
*Some* browsers put it in, unless you disable their 'Attempt telepathy'
misfeature. I find it intensely annoying when a browser re-interprets
the URL that I type - for example asuming that instead of a URL I
intended a search-term, and further that the search engine I had in mind
was somewhere.silly.msn.com.
>
It isn't necessary at all. These prefixes don't do anything. They're
just names.
I'm sure Harlan knows what he means, but I think what he's said above is
misleading.
If the host providing the webservice is
www.example.org, and there is no
CNAME record aliasing that name to some other name, then the www. *is*
necessary. The 'prefix' isn't a prefix; it's the name of the host.
A location in the domain-name tree is just that - a named node. The name
may correspond to a host, if there is an A record in DNS, or if there is
a CNAME record that aliases that name to another name that does have an
A record. And the same name may have child nodes, which have the same
status - they may or may not represent hosts, and they may or may not
have child nodes.
So a node may represent both a host and a 'domain' in the colloquial
sense. In fact a 'domain' in DNS-speak is simply a location in the tree
of names - i.e. a node. I think this may be why people find the term
"FQDN" (standing for "fully-qualified domain name") confusing - in this
context a "domain name" means a name in the domain name system. For some
time I used to think it referred to the name of the domain in which a
host resided - I didn't realise a FQDN could mean specifically the
fully-qualified name of a host.
It is common practice to create an A record for the parent domain ('e.g.
example.com), and to also create a CNAME for
www.example.com, that
points to example.com. If you do this, then both names will resolve to
the same host. In the address-bar of your browser, request to
www.example.com will continue to point to that domain as you navigate
the site, and similarly a request to the naked example.com will preserve
that nme in the address-bar.
>
An organization will generally have a domain, like example.com, to
which their servers will belong. Then they name the servers anything
they want:
fidelio.example.com pagliacci.example.com tosca.example.com
For servers that have specific purposes, particular the ones being
exposed to the public (in other words, not only accessible from the
internal LAN), they'll typically assign server names that denote the
use of the server:
www.example.com mail.example.com webservices.example.com
That's all. It's all a matter of convention. If you defined
mail.example.com to point to your web server, everything would work.
If you have three different web sites and you call them
general.example.com shop.example.com returns.example.com
everything is fine. You can also use example.com, naked, as a server
name.
It is important to note that if the DNS zone is example.com, and you
wish to establish a host at that node, then you MUST use an A record.
You may not use a CNAME to identify the host that shares a name with the
zone, and have it point to another name (e.g.
www.example.com) that has
the A record. Doing it that way round causes problems.
Since the different services (web, mail, etc.) use different default
ports, you can even use one name for all of them, and skip the prefix
altogether. You can also assign multiple names to the same server, so
that example.com and www.example.com, typed into a web browser, both
lead to the same web site. It's all completely flexible.
This would be the case if the two names had A records pointing to the
same address. This can cause problems in certin cases; it is a very good
idea to have reverse DNS on a mailserver that matches the server's A
record, for example. Since you can only have one rDNS record for one
address, it is impossible to guarantee a match, if the server has
multiple A records.
Where a single host has multiple IP addresses, e.g. multiple network
interfaces, the situation is more complicated, and I understand there is
some controversy as to whether it is good or bad practice to give the
interfaces different names.
>
>So, how can putting "www" into a link break it as a link?
It isn't breaking anything. This is what will happen if the name
example.com has been defined to denote a web server, and the name
www.example.com hasn't been defined. Each name has to be configured
to exist.
--
Jack.
http://www.jackpot.uk.net/