Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!spool.mu.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!ub!uhura.cc.rochester.edu!rochester!kodak!uupsi!sunic!ugle.unit.no!hanche
From: hanche@imf.unit.no (Harald Hanche-Olsen)
Newsgroups: comp.sys.apollo
Subject: Using name servers (was: Internet Address of dabo.ifs.umich.edu)
Message-ID: <HANCHE.91Feb18195355@hufsa.imf.unit.no>
Date: 18 Feb 91 18:53:55 GMT
References: <1991Feb15.232459.25388@jato.jpl.nasa.gov>
	<4fe14e43.1bc5b@pisa.ifs.umich.edu>
Sender: news@ugle.unit.no
Organization: The Norwegian Institute of Technology, Trondheim, Norway.
Lines: 26
In-Reply-To: rees@pisa.ifs.umich.edu's message of 18 Feb 91 04:11:41 GMT

In article <4fe14e43.1bc5b@pisa.ifs.umich.edu> rees@pisa.ifs.umich.edu (Jim Rees) writes:

   Uncomment the 'nmconfig' lines in /etc/rc.local.  Create the empty file
   /etc/daemons/nmconfig.  Create the file /etc/resolv.conf.  It should look
   like this:

   domain  domain-name
   nameserver      server1
   nameserver      server2
   nameserver      server3

   where domain-name is your domain name, and server1..n are the numeric IP
   addresses of your name servers.  You can have as many as you want, it tries
   them in the order listed.

That's what the manual says.  Last time our primary name server became
unavailable, our machines would not revert to the second one and so
most addresses were rejected as `unknown'.  Yes I did check that the
second name server was up and responsive.  Guess I should have APR'd
it, but then I snowed under in other chores and the primary name
server has never been off-line since...

- Harald Hanche-Olsen <hanche@imf.unit.no>
  Division of Mathematical Sciences
  The Norwegian Institute of Technology
  N-7034 Trondheim, NORWAY