Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!decwrl!sgi!shinobu!odin!camelot!jesse
From: jesse@camelot.sgi.com (Jesse Rendleman)
Newsgroups: comp.sys.sgi
Subject: Re: weird interaction between 4sight and the dns resolver.
Message-ID: <1991Feb14.162200.16200@odin.corp.sgi.com>
Date: 14 Feb 91 16:22:00 GMT
References: <44593@nigel.ee.udel.edu>
Sender: news@odin.corp.sgi.com (Net News)
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 22

In article <44593@nigel.ee.udel.edu> tom@cis.udel.edu (tom) writes:
< description of dns/4sight problems >

Our window server requires the following four lookups to succeed, 
(assume "bob" is your machine name, and 1.2.3.4 is its IP address)

1) nslookup localhost
2) nslookup bob
3) nslookup -q=ptr 127.0.0.1
4) nslookup -q=ptr 1.2.3.4

If any fail, the setup files on the nameserver(s) you point to need to
be adjusted.

As of Irix 3.3, my favorite workaround to this problem is to put:

    hostresorder local bind

before the nameservers in your resolv.conf file.  This causes your
local /etc/hosts file to be searched (where you can keep definitions
for localhost and "bob") before dns.  More info on this feature can
be found in the resolver(4) man page.