greg@sif.claremont.edu (Tigger) (05/14/91)
As the network manager here, I am currently in the process of planning our
NetInfo network, and having read the _Network and System Administration_
manual this weekend, I have a question.
First a bit of background. The Claremont Colleges consist of six independant
campuses that share certain central facilities, such as a main library and
physical plant. On the computer side we share an intercampus fiber optic
network backbone and Internet and BITNET connections. Other than that, and
except for cross registered students, we do not share academic computing
departments or facilities.
Clearly we need at least a three-level NetInfo domain hierarchy. On page
104 of _Network and System Administration_, in the "Setting Up Mail on a
NetInfo Network" section of Chapter 7, the second paragraph introduces
the concept of a mail server, and states
MailManager dictates that this computer be the master
NetInfo server for the network. (If you have a three-
level or more domain hierarchy, this machine should be
the master NetInfo server for the "/" domain.)
The key question results from the fact that the first sentence is an
imperitive, but does not say precisely what the definition of "the network"
is. The second sentence uses the word "should." Is this just a
recommendation, or was that word used just for grammatical variety, and
should it really have been "must?" In other words, can the master NetInfo
server for each of the second-level domains function as the mail server?
From a logical perspective, I think the answer to that question must be "yes."
In our situation, the "/" NetInfo domain would essentially hold no information.
Each of the campuses would have their own second-level domain, where all user
information and such would reside. There may in fact be two or more users
who have the same account name, one in each of the second-level domains. If
the mail server were the "/" NetInfo server, how would it know which user
was the proper recipient of the mail? I suppose it could check the node
address of the message and deliver it to the user who logs on to any of the
nodes in the same NetInfo domain, but that seems rather more difficult than
simply allowing a master NetInfo server of *any* NetInfo domain level to be
a mail server for that domain.
Does anyone know the answer? Has anyone actually tried it? I cannot believe
that I am the first one to ask. There are enough large organizations out
there in both the educational and business worlds that there are going to
be plenty of three-level or more NetInfo domain hierarchies where there are
going to be numerous reasons why the domains cannot share a mail server.
The very design of the NetInfo domain and server structure clearly shows that
this situation was foreseen.
So, any information would be greatly appreciated, especially from anyone
who has actually done what I am proposing. Please e-mail me directly (with
standard mail, not NeXTmail; our first machine isn't on the net and may not
be until all this is resolved), and I will post a summary to the net.
Greg Orman greg@pomona.claremont.edu
Systems Manager greg@pomona.bitnet
Seaver Academic Computing Services
Pomona College Standard disclaimer-type stuff