Well, this turned out to be a silly question. Thanks to:
Tim Carlson <firstname.lastname@example.org>
Craig Russell <email@example.com>
Barry Gamblin <firstname.lastname@example.org>
for pointing out that sendmail routes based on DNS domains, *not* NIS domains.
With the appropriate host and configuration file changes, mailing now works
>We've got four Ultra 2 servers and an SS20, all running Solaris 2.6 (the 5/99
>update), and a number of X terminals. These are all on the same subnet and
>all in the same NIS domain, digicomp.com .
>I've been attempting to set up a second NIS domain on the same subnet for a
>couple of E250's and ten Ultra 5's (all running Solaris 7), which I want to
>keep separate from our original NIS domain, as these are project machines and
>will be disappearing soon (when they go onsite, I want them to be using their
>own NIS domain rather than ours -- thought I'd try the setup here first).
>So I've set the default domain on these project machines to be proc.pr, and
>everything seems to be running OK, except I can't send mail between the two
>domains. Whenever I try to send to one of the proc.pr machines, the
>(me) gets a bounce message saying "...<digicomp.com>... Sender domain must
>resolve", and whenever I try to send from a proc.pr machine, the bounce
>reads, "...<proc.pr>... Sender domain must exist"
>So I guess my question is, how do I get sendmail to recognize the new NIS
>domain? Or is this indicative of some screwup I've made in setting up the new
-- Bill Fenwick Email: email@example.com Digicomp Research Voice: (607) 273-5900 ext 32
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:26 CDT