UPDATE: Problem - DNS/NIS in mixed Solaris SunOS environment

larry (larry@ca.cch.com)
Thu, 22 May 1997 10:32:32 -0400

I think I have a better handle on the actual problem now. It seems to
be the NIS forwarding to DNS for unknown hostname resolution that is
broken.

The reason I think so is the mod in the nsswitch.conf file that got
stuff working on the Solaris platform ie: changing the hosts line to
read:

hosts: nis dns [NOTFOUND=return] files

as opposed to the original:

hosts: nis [NOTFOUND=return] files

I have been racking my brains for any changes that I might have made
around the time that this all stopped working, but I can think of nary
a one - hence the process of trying to figure out what is broken.

I've had a few kind souls make suggestions, but none of them have
proven to be the solution.

The suggestions were:

- check ypbind on the clients and make sure it is running
it is.

- patch the SunOs resolver libraries
don't think this is the problem since it seems to be the NIS
forwarding to DNS that is broken. I think the libresolv patches
are for non-NIS clients be able to directly resolve via DNS -
corrections ?

- check for ypserv running with a -d
it is

- check for out of date NIS server.
did that - reinitialized maps on the server and pushed to the
secondaries just to make sure.

anyone else ? I'm getting really desparate.

Thu May 22 10:30:57 EDT 1997
=====================================================================
Larry Chin {Larry_Chin@ca.cch.com} CCH Canadian Ltd.
Phone: 416-224-2224 ext. 6349 90 Sheppard Ave E
Fax: 416-224-1414 North York, Ontario, M2N 3A1
=====================================================================

Scott's second Law:
When an error has been detected and corrected, it will be found
to have been wrong in the first place.
Corollary:
After the correction has been found in error, it will be
impossible to fit the original quantity back into the
equation.