From: denouden@cs.utwente.nl (Jan den Ouden)
Subject: nameserver example
Keywords: named nameserver bind 
Organization: University of Twente, Dept. of Computer Science
Date: Sat, 9 Jan 1993 01:26:43 GMT

Hi

A while ago I posted a couple of messages concerning the setup
of the named daemon config. files for a simple isolated 
network with a local nameserver. Since nobody responded with
a ready-to-go solution I decided to dig a little deeper into
the subject. As a result I've now got a working nameserver.
This message describes the changes I made. Here goes:

General.
--------
My isolated network consists of 2 machines, called whisky
and jenever which are both located in the domain vdm. Whisky
has IP address 128.0.0.1 and jenever has IP address 128.0.0.4.
The nameserver runs on whisky, and jenever accesses whisky to
resolve names.

Starting point is SLS 0.98pl5. This distribution contains
install.net and hostcvt, which are supposed to make network
installation easier, but they where of no help to me. Instead,
I manually changed the files concerned.

Common changes to files for both machines.
------------------------------------------

/bin/hostname machine_name added to /etc/rc. Machine_name
stands for either whisky or jenever. This command should
be placed before the /bin/sh rc.local command. Further 
hostname commands removed from /etc/rc and /etc/rc.local.

In /etc/inet/rc.net HOSTNAME=softland changed to 
HOSTNAME=machine_name. Commented out the IPADDR= line 
and inserted IPADDR=128.0.0.1 or IPADDR=128.0.0.4.

ROUTER set to 0.0.0.0 and NET set to 128.0.0.0. In the
third $CONFIG line eth0 changed into eth_if (I use an
Artisoft network card, this isn't necessary for standard
WD network cards).

Changes for the nameserver (whisky in my case).
-----------------------------------------------

For a nameserver the portmap, inetd and named daemons
should be started. This is done in the /etc/inet/rc.net
file.

named.boot contains 
-----------------------------------------------------
directory	/etc/inet

domain		vdm
primary		vdm			named.hosts
primary		0.0.128.in-addr.arpa	named.rev
primary		0.0.127.in-addr.arpa	named.local
-----------------------------------------------------

named.hosts contains
-----------------------------------------------------
@	    IN   SOA  whisky.vdm.  root.whisky.vdm. (
		  1    ; Serial
		  3600 ; Refresh
		  300  ; Retry
		  3600000   ; Expire
		  14400 )   ; Minimum

	IN	NS	whisky.vdm.

localhost	IN	A	127.0.0.1
whisky		IN	A	128.0.0.1
jenever		IN	A	128.0.0.4
-----------------------------------------------------

named.rev contains
------------------------------------------------------
@	IN	SOA	whisky.vdm. root.whisky.vdm. (
			1 ;
			3600 ;
			300 ;
			3600000 ;
			3600 ) 

	IN	NS	whisky.vdm.

1	IN	PTR	whisky.vdm.
4	IN	PTR	jenever.vdm.
------------------------------------------------------

named.local contains
----------------------------------------------------------
@	IN	SOA	whisky.vdm.	root.whisky.vdm. (
			1;
			36000;
			3600;
			3600000;
			36000;
			)

	IN	NS	whisky.vdm.
1	IN	PTR	localhost.
----------------------------------------------------------

Changes for a non-nameserver (jenever in my case).
--------------------------------------------------

For a non-nameserver only the portmap and inetd daemons
have to be started. The startup of the named daemon in
/etc/inet/rc.net can thus be commented out.

A non-nameserver depends on a nameserver for name
resolution. The non-nameserver is directed to a name-
server by the /etc/inet/resolv.conf file (NOT the
/etc/resolv.conf as mentioned in a lot of doc. files).

So, the /etc/inet/resolv.conf file on jenever contains:
---------------------
domain vdm
nameserver 128.0.0.1
---------------------

That's all. 

I'm currently trying to get NFS working.
Newsgroups: comp.os.linux