Newsgroups: comp.protocols.tcp-ip
Path: utzoo!utgpu!watserv1!watmath!att!linac!mp.cs.niu.edu!rickert
From: rickert@mp.cs.niu.edu (Neil Rickert)
Subject: Re: Confirming DNS name - what I really meant
Message-ID: <1991May31.161200.25995@mp.cs.niu.edu>
Organization: Northern Illinois University
References: <895@bcstec.boeing.com>
Distribution: na
Date: Fri, 31 May 1991 16:12:00 GMT
Lines: 25

In article <895@bcstec.boeing.com> ced@bcstec.uucp (Charles Derykus) writes:
>
>My intent was to ensure that DNS matched machine x with its "real" name -
>what was configured in smtp and hopefully the same as the /etc/hosts name
>used for host name initialization during booting. If machine x's smtp name
>mismatchs DNS's name for machine "x", won't mail delivery to "x" misfire
>for example?

 If this kind of mismatch were so serious, probably half of the machines on
Internet would be unable to handle mail.  Actually you can usually tell
from the syslog entries or the 'Received:' headers whether your mailer
received mail from a system whose smtp name is different from its DNS
name.  The proportion of my syslog records showing this is not very high,
but that is because most of these misconfigured systems send their mail
to another system to forward it for them.

 If you are using 'sendmail', the SMTP name is determined by the $j
macro.  With most configuration setups, the handling of mail to your
domain is dependent on the class $=w, or perhaps $=w.$m .

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