On Thu, 2008-11-27 at 16:20 -0500, Sam Varshavchik wrote: > Ricardo Kleemann writes: > > > Thanks Sam. > > > > But if I'm connecting to localhost, how does that play into reverse DNS? > > It doesn't matter what your IP address is. Courier still attempts to resolve > it. The only thing that's special about localhost is that it's IP address is > 127.0.0.1 > > > The server is behind a firewall so the actual connecting address would > > be an internal IP anyway. But in the case of localhost I don't > > understand the role of reverse DNS and ident lookup. > > Courier performs reverse/forward DNS lookup on the connecting IP address. > Whether it's localhost, or some other IP address, it doesn't make a > difference.
Ok, I see. So how typically does localhost resolve in reverse DNS? I am using a dnscache in my firewall, I'm not sure how to make that work with reverse DNS, anyone know? Ricardo ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
