Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!decwrl!mcnc!rock.concert.net!sunvis.rtpnc.epa.gov!fty
From: fty@sunvis.rtpnc.epa.gov (Frank Terhaar-Yonkers)
Newsgroups: comp.sys.sgi
Subject: Re: weird interaction between 4sight and the dns resolver.
Message-ID: <1991Feb14.130946.16262@rock.concert.net>
Date: 14 Feb 91 13:09:46 GMT
References: <44593@nigel.ee.udel.edu>
Sender: news@rock.concert.net
Reply-To: fty@sunvis.rtpnc.epa.gov (Frank Terhaar-Yonkers)
Organization: U.S. Environmental Protection Agency
Lines: 19

I had the same problem.  It manifested itself when the primary NS 
machine which is in the SAME domain as the 4D was down.   So ... it went
to the secondary server which is on a different domain/network.  The resolution
it gets is then: localhost."domain of secondary server", instead of:
localhost."domain of primary server".  I kludged around the problem by putting the
following in /usr/etc/resolv.conf: 
hostresorder    local bind

and the following in /etc/hosts:
127.0.0.1       localhost localhost.rtpnc.epa.gov

Bind should then no longer resolve "localhost". 

I wish I knew the REAL problem (probably an error in the way the DNS stuff is
set up) but don't have the time to persue it.

-- 

cheers - Frank