On Thu, 21 Jun 2001 20:23, Edward Barrow wrote:
> This one should be really easy, but it has me baffled. I'm supposed to
> give my computer a "fully-qualified host name", and I don't know what name
> to give it.
>
> At the moment it is not connected to the Internet so I don't suppose it is
> that important, but when I do get it connected (a task that will involve
> recompiling the kernel with support for the Alcatel ADSL USB modem & I
> anticipate much grief) it probably will. On the other hand, I won't be
> using the system to provide any services outside the local area network
> (192.168.1.0); my website is remotely hosted and I collect my mail from a
> remote server, so no external clients need to use DNS to find my machine.
>
> An additional possible complication: I use one ISP - call it isp.com -
> for the connection (and outgoing mail); another company (call it
> hostingco.com) hosts my webspace and mailboxes; while a third
> (domainco.com) provides my domain names and forwards mail and http to
> hostingco.com. (It just worked out cheaper that way).
>
> So should the fully qualified host name be:
>
> myhost.isp.com
> myhost.hostingco.com
>
> or
>
> myhost.mydomain.com (where mydomain is registered with domainco.com)
>
> Or doesn't it matter?
>
> And where does the Samba workgroup name come in?
The hostname is what your computer will be called on a network. It is
synonymous with a "computer name" in Windows. It doesn't really matter what
the hostname is -- you could call your computer "Bob" if you really wanted.
--
Sridhar Dhanapalan.
"There are two major products that come from Berkeley:
LSD and UNIX. We don't believe this to be a coincidence."
-- Jeremy S. Anderson
