On Fri, 13 Nov 1998, Andromeda wrote:
> I was made aware of the fact that a host does not necessarily have to
> answer with a hostname, but with an IP. Now, I read the documentation which
> stated that if I add the "no_refuse_ip_options" keyword to my configuration
> it would take care of that.
Be aware that refuse_ip_options has absolutely nothing to do with the
problem you describe. It is concerned with host masquerading at the IP
packet level. I don't think the documentation is confusing on this
point, but if you feel it is, please explain where the confusion arises.
I think your statement "a host does not necessarily have to answer with
a hostname, but with an IP" indicates a bit of confusion. What
actually happens is that at the start of an IP connection, the receiving
host is given the IP address of the calling host. That is all. If it
wants to, it can try to look up the host name by interrogating the DNS
and/or calling gethostbyname(). Exim does this when it needs to know the
host name. It calls gethostbyname(), which on most systems calls the DNS
if it doesn't have local information about the name/address connection.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
--
*** Exim information can be found at
http://www.exim.org/ ***
