Linux

You don't necessarily need to have DNS running. Since it's just for internal use, your users can connect to your Intranet with http://192.16.128.1 (or whatever is the IP address of the box).

If you really want to use DNS, then just use BIND. Yourdistribution of Linux may have come with BIND. Otherwise, you'll need to download it, and install it. Check out the manpages for complete help on BIND. Just note that you want your DNS to "be authoritative for your domain".

Tip: you do NOT have to call your domain "mycompany.com". You can just call your root domain "mycompany", as long as you never expect to broadcast this onto the Internet (where it will simply be ignored). In this latter case, your Intranet server can be known as "intranet" in this domain using a "Host record" that points to its IP address. Then it can be reached with "http://intranet.mycompany" (or "http://intranet.mycompany.com" if you go the standard route).

I do a lot of DNS work. First you will need to set up a DNS name server for your internal users. That could be any server you already have - Linux, Unix, NT, etc. The first step is to go to www.isc.org and download the latest released version of bind for the platform you decided to insall on and follow the directions in the readme files to install it. The next thing you will have to do is set up at least one zone (sounds like one is good enough for what you want to do) in forward and reverse lookup format. Then you need to set up your bind configuration files for the level of security and logging you wish to implement and to have them point to the proper zone files. It sounds like if you keep this internal and are on a private network or are protected via firewall you can keep this pretty simple. Finally, you will just need to go to your PCs and anyone that needs to use this intranet and direct them to the DNS server. This sounds like a lot, but once you get the plan down it can all be done in a day. If you are using DHCP for the PCs at your site it is a lot easier because you can have DHCP assign the DNS information. If you are completely new to this I can guide you through these steps. Just email me at my alias. To get you started login to the machine you will install DNS on and ftp ftp.isc.org. You can log in as anonymous. Then cd /isc/bind/src/cur/bind-8. Once you are there do an ls and you should see three files ending in .gz and three ending in .gz.asc.Get the three ending in .gz. After they are on your system you can gunzip them and tar xvf them to get them into readable format. They will have readme files. The bind-src is the one you will definitely need to install. The contrib and doc are just documentation, but are good to have. Once you are at this point you will probably want to ask more questions about installing these files so feel free to email me.

Bob is right. If you aren't comfortable with DNS, then just use the IP address.

You should be able to copy your pages into /var/spool/http (at least on Red Hat), and then start up Apache, and you're set.

Kev.

Use NT and setup a WINS server. This will be your easiest solution. If you already have an NT server setup on the internal LAN, then it won't take much work. WINS works great, unless your workstations are linux too.

This question was closed by the author