[comp.sys.sgi] weird interaction between 4sight and the dns resolver.

fty@sunvis.rtpnc.epa.gov (Frank Terhaar-Yonkers) (02/14/91)

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

jesse@camelot.sgi.com (Jesse Rendleman) (02/15/91)

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.