Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!news.cs.indiana.edu!att!linac!mp.cs.niu.edu!rickert
From: rickert@mp.cs.niu.edu (Neil Rickert)
Newsgroups: comp.mail.sendmail
Subject: Re: Temporarily disable MX usage
Message-ID: <1991Feb21.173954.907@mp.cs.niu.edu>
Date: 21 Feb 91 17:39:54 GMT
References: <1991Feb21.181945.3595@rusmv1.rus.uni-stuttgart.de>
Organization: Northern Illinois University
Lines: 29

In article <1991Feb21.181945.3595@rusmv1.rus.uni-stuttgart.de> wolf@grasp2.univ-lyon1.fr (Christophe Wolfhugel) writes:
>My current sendmail.cf uses MX records (OK ALL in fact). Through tries,
>I've seen that MX resolution is done on the really last statement, the
>$#tcp at the end of rule 0  (in some cases it's done before, but that
>does not interest me)..
>
>Due to the really heavy traffic I general, I wish not to use the MX
>records for certain category of hosts: our local systems.
>
>Is there any mean for temporarily disabling MX usage? (if in my domain
>then do not resolve).

  Bad idea.  The MX records are there to say where mail should go.  Not
using them is likely to cause misdirected mail.  The only time you should
not be using them is when you have specifically arranged some other way of
getting the mail to that host, such as by UUCP.  In that case you would need
special treatment in 'sendmail.cf'.

  If you are worried about the time for reading nameserver records, just
make sure you have your own nameserver running, and make in an unofficial
secondary server for your own domain.  It will download the data for your
domain from a primary server, and have it readily available for fast lookups
when needed.

-- 
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
  Neil W. Rickert, Computer Science               <rickert@cs.niu.edu>
  Northern Illinois Univ.
  DeKalb, IL 60115                                   +1-815-753-6940