On Tue, 7 Feb 2006, Thomas Lohman wrote:
I just tried to do
a reverse lookup of the IP address of the client and it hung and eventually
timed out. What is the best solution to this? To somehow cache these
addresses or is there a way to turn off this reverse lookup?
The first and best thing to try is to fix whatever is making the DNS fail.
In the case of the server's own name, it's probably best to make sure that
/etc/hosts is set up properly. Note that the FQDN *must* be first; many
Solaris systems are set up with a non-FQDN first.
Fixing the DNS is also a good idea.
In your case, if you aren't in a position to fix the client's DNS address,
you may be forced to turn off reverse DNS lookups. I advise against doing
so except as a LAST RESORT; it will make the logs less useful and it will
break Kerberos authentication.
However, if you absolutely, positively, must, the thing to change is
allowreversedns; it is set to T (allow it) and you would change it to NIL.
The file is imap-****/src/osdep/unix/tcp_unix.c
Even if you find yourself forced to do this, I strongly advise that you
try to get the DNS fixed (including, but not limited, to nagging the
client network manager). You may want to do something like have an imapd
that does this be on an alternative port, or some other such mechanism so
that most usage does the reverse DNS correctly.
-- Mark --
http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
