Return to BSD News archive
Newsgroups: comp.unix.bsd.freebsd.misc
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.bhp.com.au!mel.dit.csiro.au!actcsiro!news.nsw.CSIRO.AU!metro!metro!inferno.mpx.com.au!news.mel.aone.net.au!imci4!newsfeed.internetmci.com!howland.reston.ans.net!ix.netcom.com!netcom.com!kientzle
From: kientzle@netcom.com
Subject: Re: [Q] resolv.conf problems
Message-ID: <kientzleDMMy65.5DL@netcom.com>
Organization: NETCOM On-line Communication Services (408 261-4700 guest)
References: <slrn4hsdhm.lbo.hgoldste@bbs.mpcs.com>
Date: Sun, 11 Feb 1996 23:49:16 GMT
Lines: 16
Sender: kientzle@netcom7.netcom.com
In article <slrn4hsdhm.lbo.hgoldste@bbs.mpcs.com>,
Howard Goldstein <hg@n2wx.ampr.org> wrote:
>Problem arises when either of the two 2.1 boxes boots up and the
>nameserver box is down. My resolv.conf file looks like this:
<snip>
>... and [hangs] one last time after sendmail is brought up.
Sendmail is particularly insistent on having access to a nameserver.
You might try running a caching nameserver on one or both of the other
2.1 boxes, one that forwards any `real' requests to the real
nameserver. That may be sufficient to boot the systems cleanly.
I found the 4.4BSD System Manager's Manual quite useful in
configuring a local nameserver to address a related problem.
- Tim