🚀 go-pugleaf

	I've just tried installing resolv.conf in the /etc directory to try and
take advantage of the numerous nameservers on our network. Unfortunatly this
installation over-rode the /etc/hosts file so that some hosts that were
previously defined were no loger defined with a name or the name on the central
nameservers was different, thus causing unexpected problems where those names
had been used in other parts of the Sequent's configuration.

	Question: Is there any way of forcing the resolver to look up
/etc/hosts first then trying the defined nameservers upon lookup failure. I
know this can be done on SUN machines but I don't know if that's merely a
difference in the workings of SUN and Sequent's resolver routines or some other
configuration file that has been defined on the SUN that's been missed on the
Sequent (The file /etc/resolv.conf was FTPed from one of our SUN's).

	We're Currently running Dynix/ptx 3.2.0 V1.3.0 on an S2000/200. Please
reply by email and all replies will be summarised for others interested in a
similar solution. Any help on this matter will be most appreciated.

Cheers.
--
 _--_|\   Paul Peterson,                            P.Peterson@ccsd.uts.EDU.AU
/      \  Systems Support Section,                          Ph: +61 2 330 2131
\_.--._/  University of Technology, Sydney,                  (Internal: x2131)
      v   PO Box 123, Boadway, NSW, 2007, Australia.       Fax: +61 2 330 1994