[comp.sys.sgi] How to make NeWS independent of nameservers?

macferrin@slsvax.harvard.edu (Kurtis MacFerrin) (10/17/90)

Hi,
	does anyone know how to make NeWS independent of nameservers? When the
nameservers here are down (which is often) it is impossible to do a login
from the console, apparently because NeWS won't start without getting a
satisfactory response from the nameserver re: the identity of localhost. It
seems pretty odd that it would do such a lookup in the first place, and the
NeWS documentation we have is pretty sparse. We're running 3.2.1 incidentally,
but we plan on updating to 3.3.1 this week.
	Thanks.

Kurtis MacFerrin	macferrin@slsvax.harvard.edu

macferrin@slsvax.harvard.edu (Kurtis MacFerrin) (10/17/90)

In article <4440@husc6.harvard.edu>, macferrin@slsvax.harvard.edu (Kurtis MacFerrin) writes...
>Hi,
>	does anyone know how to make NeWS independent of nameservers? When the
>nameservers here are down (which is often) it is impossible to do a login
>from the console, apparently because NeWS won't start without getting a
>satisfactory response from the nameserver re: the identity of localhost. It

Thanks to Mark Callow and Dave Hinds for the answer: under irix 3.3 a new entry
can be placed in /usr/etc/resolv.conf: hostresorder local bind. This means
that /etc/hosts is checked before the bind nameservers are queried, and should
fix my problem.

John Merritt had another suggestion that might work: run named, and put 
nameserver 0 in the first line of /usr/etc/resolv.conf.

Kurtis MacFerrin	macferrin@slsvax.harvard.edu

SOFPJF@VM.UOGUELPH.CA (Peter Jaspers-Fayer) (10/19/90)

>>  does anyone know how to make NeWS independent of nameservers? ...
>
>Thanks to Mark Callow and Dave Hinds ...: under irix 3.3 a new entry
>can be placed in /usr/etc/resolv.conf: hostresorder local bind. ...

But be aware that if you do so, the mere existence of  /usr/etc/resolv.conf
causes the grahic interface [System][System Manager][Networking] to give up
and display  "... The /usr/etc/resolv.conf file exists ... you are not able
to run this tool".   I called this in, and they gave me a song and dance on
how you can really mess  up your system with this file (true), and that the
networking tool was being re-written to allow coexistance with resolv.conf.