NIS and sendmail problems!!!

2007-12-25 11:08:00

My origional question -

~~~~~~~~~~~~~~~~

> Hi Sun Managers,

>

> After upgrading my solaris 2.6 and 2.5.1 servers to the latest y2k

> patches, I find myself tackeling a couple of weired (I think so)

> problems. Here they are for your expert inputs / solutions (preferably

> in a step-by-step, human readable fashion).

>

> 1. Prior to installation of patches, all the machines which are member

> of one NIS domain - VADER, were able to lookup/browse/telnet/ping/ftp

> etc. hosts on the internet through NIS resolution (I had the -b flag for

> makedbm set on my nis master). This has stopped now. Any clues/solutions

> to make it work again. My DNS domain is "riverrun.com"

>

> For your information, my NIS master is / has -

>

> o Solaris 2.5.1with latest Y2K patches

> o Entry in /etc/nsswitch.conf file which says - hosts: files nis dns

> o Compiled with the B=-b option in /var/yp/Makefile for makedbm

> o Correct default gateway and /etc/resolv.conf file

> o ypserver starts with -d option

>

> My NIS clients (a mixture of Solaris 2.5.1 and Solaris 2.6) have -

>

> o Latest Y2K patches

> o /etc/nsswitch.conf with - hosts: nis [NOTFOUND=return] files

>

> 2. The mail relay hosts now sends mails as user@mailhost.VADER, earlier

> behaviour was to send it as user@riverrun.com. Any pointers here? I

> would like it to be configured in such a way that all mails going out of

> the mail relay should have user@riverrun.com as their default Mail-from

> address. Again, I am looking for step-by-step instructions. FYI, my NIS

> master and mailhost are same machine. DNS however, is on a different

> machine which is not a part of NIS.

======================================================

Special thanks to : -

                            "Otto, Doug" <otto@alldata.com>

                            David Foster <foster@dim.ucsd.edu>

Who pointed out that the patches replace the origional sendmail.cf and

rename it as sendmail.cf.old.

However, my first question still remains un-answered. I'd be grateful to

anyone who can extend a helping hand. For now, I have modified the

/etc/resolv.conf file on all the client machines to use dns along with nis

for name resolution, but THIS IS NOT WHAT I WANT!!!

MANNU

Comments

Got something to say?

You must be logged in to post a comment.