\pard\tx360\tx6120\f3\b0\i0\ul0\fs28 domain name BIND mail sendmail resolv.conf mailhost\
\
Q: How should I set up mail on a existing network? How do I get domain name resolution from a known domain name server? What are the differences between the sendmail files?\
\
A: This is a multiple-step procedure that should be done with the help of a local system administrator. You need to know the hostnames and IP addresses of the servers and other information of your net. All the changes need to be done by root.\
\
\b Domain name BINDing on a client machine:\
\b0 \
You need to setup
\f1 /etc/resolv.conf
\f3 . There is a man page for resolver(5). Here is a quick overview of what needs to be set up.
\f1 /etc/resolv.conf
\f3 takes lines of two forms. One line specifies the domain name. The other lines indicate which machine serves the binding. A typical
The domain name server machine needs to know the hostnames and IP addresses of its clients. See SysAdmin/ApD_BIND.wn for details on how to set up a domain name server. Note that this might differ on your domain name server depending on what version of BIND you run on your net. Setting up a domain name server won't be discussed here.\
\
The domain name binder appends the domain name to local machines. Entries in the NetInfo machines directory shouldn't have the domain name appended to them, if there's only one value for the name property. You can have domain-appended hosts by adding them as a second value for the name property in the NetInfo machines directory. A typical entry in NetInfo would then look like this:\
\
\pard\tx1120\tx6120\f1\li720 myhost#
\b niutil -read
\i domain
\i0 /machines/
\i hostname
\b0\i0 \
ip_address: 129.18.11.199 \
name:
\i hostname
\i0
\i hostname
\i0 .next.com\
\pard\tx360\tx6120\f3\b \
\b0 Note that there might be additional properties listed (such as a
\b serves
\b0 property).\
\
\b Possible sendmail setups:
\b0 \
\
\i sendmail.subsidiary.cf
\i0 is the default configuration file. Local mail is delivered locally, mail to machines in the local domain is delivered directly to those machines, and mail to machines in any other domains is forwarded to “mailhost.”\
\
\i sendmail.sharedsubsidiary.cf
\i0 is used if you mount the directory
\f1 /usr/spool/mail
\f3 from “mailhost.” It delivers mail to machines in the local domain directly to those machines. All other mail (local mail and non-local domains) goes to “mailhost.”\
\
\i sendmail.mailhost.cf
\i0 is used on the machine that is the mailhost. It tries to deliver all mail directly to its location. You can edit this file to specify an even smarter mail relay to handle the addresses the mailhost doesn't understand.\
\
\b Connect to a known mailhost:\
\b0 \
• Launch NetInfoManager and add the host that you know to act as a mailhost to the machines directory in the appropriate domain (likely the root domain); add “mailhost” as its second hostname in the name property. The NetInfo database entry might look like:\
\
\pard\tx1120\tx6120\f1\li720 myhost#
\b niutil -read
\i domain
\i0 /machines/mailhost
\b0 \
ip_address: 129.18.11.199 \
name:
\i hostname
\i0
\i hostname
\i0 .next.com mailhost\
\pard\tx360\tx6120\f3 \
(As above, there might be additional properties listed.)\
\
• Set the sendmail.cf link to reference the correct file\
\pard\tx360\tx6120\f3 Mail will be sent in the way described above. A local machine is known as such if it has no domain appended to it and doesn't contain any `.' — for example, “mymachine” is local and “mymachine.foo.com” is not.\
\
\b Setting up a mailhost:\
\
\b0 This is described in the Network and System Administration booklet, chapter 5. However, neither
