---

Hej

Jeg har fundet en name sever som jeg tro der kan bruges.
Jeg skal bruge en local name sever, så jeg har fundet en lille freware
som jeg tro kan bruges.
http://www.tavi.co.uk/os2pages/utils/named.zip
Da jeg ikke har nogen viden om hvordan det virker. så prøver jeg om der
er en som vil bruge lidt tid på at hjælpe. Det jeg gerne vil er hvordan
skal min maned.cfg se ud.

Nit netvæek er som følgede.

Lokal peer sever.
TeamNord
192.168.0.50 255.255.255.0

client 1
NEW2000
192.168.0.30 255.255.255.0

Client 2
X3000
192.168.0.40 255.255.255.0

Client 3
X2000
192.168.0.60 255.255.255.0

Client 4
X4000
192.168.0.70 255.255.255.0

Client 5
X1000
192.168.0.80 255.255.255.0

Client 6
X5000
192.168.0.90 255.255.255.0

Client 7
192.168.0.20 255.255.255.0

client 8
X6000
192.168.0.10 255.255.255.0


opsætning fil fra name sever som er forklaring=

#
# local network address
#
auth_network 192.168.42.0
#
# mask for local addresses
#
auth_netmask 255.255.255.0
#
# local domain name
#
auth_domain abc.xyz.com
#
# interface that must be up if name requests are to be referred on
#
refer_interface sl0
#
# name server addresses for ISP 1
# (if address associated with sl0 is 192.168.33.x, where x is anything,
# use nameserver 192.168.33.47
#
refer_servers 192.168.33.0 255.255.255.0 192.168.33.47


name.doc

A simple name server for OS/2
=============================

Introduction
------------
This package contains a very simple domain name server for OS/2. It is
intended primarily for small networks which access the Internet via a
dialup connection (where another, real name server will also be used).

The name database is, simply, the HOSTS file normally used by the OS/2
name resolution library. However, if the dialup connection is active,
then another name server (typically that at the ISP) can be consulted as
well.

There are other, more sophisticated, name server programs available;
this one is, however, small, fast and free!

How does name resolution work?
------------------------------
Normally, OS/2 does name resolution by consulting a set of name servers
(specified via the RESOLV2 file) and/or by looking at a static list of
hosts in the HOSTS file. By default, the name server is consulted
first, but this means that a different RESOLV2 file is needed when the
dialup connection is not active. This search order can be overridden by
putting:

SET USE_HOSTS_FIRST=1

in CONFIG.SYS, but it is more convenient to use a small local server
that can pass on queries to another name server if it is available.
This eliminates tiresome delays waiting for timeouts.

Setting up the server
=====================
Installation and setting up of the server is very easy.

Step 1
------
Copy the program files into place. Copy NAMED.EXE to any suitable
directory; it is convenient if this directory is on the PATH. Also,
copy NETLIB.DLL to a directory that is on the LIBPATH.

Step 2
------Locate the ETC directory used by TCP/IP. If you don't know the
location
of this directory, type the command:

SET ETC

at an OS/2 command prompt. You need to create one file in this
directory. We'll call this the ETC directory from now on.

Step 3
------
Create the NAMED configuration file. This must be called NAMED.CNF, and
must reside in the ETC directory.

The format of the configuration file is very simple. Items within lines
are separated by any number of space or tab characters (as long as there
is at least one). Anything on a line after (and including) a '#'
character is ignored. Each line starts with a command, followed by
parameters which depend on the command. Commands are as below: items in
<>
indicate values to be inserted. Commands don't have to be in upper case.

PORT <portnumber>
This indicates the port on which NAMED should listen. Normally