Domains & networking

Right. I know a reasonable amount about Linux/Unix, Windows and Mac,
Apache, PHP, HTML, bits of C(++) but my knowledge of DNS and networking
is pretty dreadful so be gentle with me here :)

Basically, can someone walk me through (or show me somewhere that will
walk me through) setting up a domain for my local network, and having
computers accessible via compname.domain.com? I actually only want one
computer accessible like that, which will be the server I'm thinking of
buying, so I can access it easily via SSH. I'd also like to be able to
host pages on the main network domain (i.e. have that domain point to a
directory on the server).

So, to clarify, I'd like:

- to selectively be able to have some computers on my network
availiable at computer.domain.com, but not neccessarily others
- to point domain.com to a directory on a server on the network
- also to be able to have subdomains on the server (i.e. have
sub.server.domain.com), and also on the main network (sub.domain.com),
all pointing to different places on the hosting server...

I have a feeling what I may be looking for is an entire introduction to
networking, so if anyone can point me towards one... :)

N.B. I don't actually have a server or (much of) a network at the
moment, this is all being planned in my head.

Thanks in advance....



Adam
General computer geek >_>

Hello,

kindredhyperion@gmail.com writes:
> So, to clarify, I'd like:
>
> - to selectively be able to have some computers on my network
> availiable at computer.domain.com, but not neccessarily others

You have first to buy a domain name. Then, find someone that can host
your DNS entries, that is, someone that can provide you nameservers,
for example www.dnsmadeeasy.com. You can too handle that yourself with
Bind or djbdns.

> - to point domain.com to a directory on a server on the network

You can link a domain name with an ip, not with a directory on a
machine. That will be your webserver (for example) that will handle
the link IP-directory.

> - also to be able to have subdomains on the server (i.e. have
> sub.server.domain.com), and also on the main network (sub.domain.com),
> all pointing to different places on the hosting server...

That feature is a part of the services that provide dns servers.

> I have a feeling what I may be looking for is an entire introduction to
> networking, so if anyone can point me towards one... :)

Here is a good introduction to dns: http://en.wikipedia.org/wiki/Dns

> Thanks in advance....

Hope this helps.
-AJ

That's wonderful, thankyou.

I was recommended http://www.zoneedit.com by another website, which
seems pretty good, but I will check out the one you suggest as well.

After following those steps then will a computer on the network be
accessible at computer.domain.com?

Hello,

Please, quote your text the next time..

kindredhyperion@gmail.com writes:
> That's wonderful, thankyou.

You're welcome.

> I was recommended http://www.zoneedit.com by another website, which
> seems pretty good, but I will check out the one you suggest as well.

zoneedit.com is free. But in my opinion, the services they provide is
not fast enough.

> After following those steps then will a computer on the network be
> accessible at computer.domain.com?

If your DNS configuration is well done, you'll be able to access your
machines. Don't forget to configure your /etc/hosts (man 5 hosts) and
other files (dependent of the system you are working on).

Hope this helps.
-AJ

On Wed, 17 May 2006 04:36:15 -0700, kindredhyperion wrote:


> I was recommended http://www.zoneedit.com by another website, which
> seems pretty good, but I will check out the one you suggest as well.

They are good and they are free. They're fast enough for my needs.

The following link might be of some use.

http://dannelson.net/LSH/domain.html

> After following those steps then will a computer on the network be
> accessible at computer.domain.com?

You have to look at it from two directions. If you buy a domain name,
then you can use a name server that's available on the internet to point
to your network's internet gateway. These are all public ip addresses.

But your internal network will have private ip addresses and will not be
visible from the internet. If you want to use DNS to access internal
clients, from inside, then you'll need a name server accessible
internally. It's not that difficult to set up. You can use the same
domain name. Have a look at the following howto.

http://www.tldp.org/HOWTO/DNS-HOWTO.html

If you want one of your internal servers, with a private ip address, to be
visible on the Internet, then you have to get your gateway computer to
port forward to it.

Dan