SUMMARY: DNS & Solaris 2.1

From: Jens Petersohn (
Date: Thu Mar 04 1993 - 08:41:19 CST

Actually this message answers to questions: One I had myself and and one I
stumbled over by accident.

1) Instability of in.named on Solaris 2.1.

        It seems that the in.named included in the Solaris 2.1 distribution
        is terribly unstable. The easiest solution for now I have discovered
        is to use the OLD (SunOS 4.1.2 in my case) in binary compatibility
        mode. This works just fine. If it's slower I can't tell.

2) Using a Solaris 2.1 host and the DNS for name resolution.

        Under SunOS 4.1 it was next to impossible to run DNS name resolution
        without either a kludge fix or the NIS (V2 I guess). Under Solaris
        2.1 it is incredibly simple, but you must ignore what the manual
        (SunOS 5.1 Administering NIS+ and DNS) says. All that is required to
        make a non-NIS host use the DNS for name resolution is to change
        the host: line in the /etc/nsswitch.conf file to the following:

        hosts: files dns [NOTFOUND=return]

        and set up a correct version of /etc/resolv.conf. You must have the
        names of machines which are somehow contacted during boot in the files
        in /etc and files must appear first in the hosts: line, otherwise
        the machine will hang during boot (at least ours did). Make sure
        that /etc/netconfig is using (It does from the factory.)

I hope this is of some use.

Jens Peterohn
(If you have non-constructive comments, I don't want to hear them.)

| Jens Petersohn | Internet: |
| Dept. of Physics and Astronomy | |
| Ritter Observatory #302 | Bitnet: jkp@uoft02 |
| University of Toledo | |
| Toledo, OH 43606 | BellNet: (419) 537-2589 (Campus ph.) |

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:07:33 CDT