John,<br>You are correct. Reverse lookup is to get a name from an IP address. A few years back in an effort to stem the spam flood, many mail servers began to require a valid reverse DNS lookup. This helped block spoofed IP addresses. It did nothing else. Due to how most ISPs now manage their networks from an IP standpoint, rogue IP addresses are not as common.<br>
<br>That said, as long as your IP address has a valid reverse lookup data, you should be OK. Most valid lookup data will basically identify the source IP address and the ISP name or ISP domain. <br><br>for instance: I have the domain name <a href="http://jimkinney.us">jimkinney.us</a> which resolves to 70.88.182.245. a dig -x shows the reverse is <a href="http://70-88-182-245-Atlanta.hfc.comcastbusiness.net">70-88-182-245-Atlanta.hfc.comcastbusiness.net</a> which identifies my IP and my ISP and my region. This seems to be quite common now.<br>
<br>Some ISPs will set your reverse DNS data to match your domain name. so far that seems to also require that your domain name be hosted with them as well.<br><br><div class="gmail_quote">On Thu, Dec 29, 2011 at 9:33 PM, John Heim <span dir="ltr"><<a href="mailto:john@johnheim.net">john@johnheim.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Wait a minute, something doesn't make sense to me. Why would a mail system<br>
do a reverse lookup as a way to prevent spam? So the smtp client connects to<br>
the mail server, the socket says the connection is from <a href="tel:66.170.20.226" value="+16617020226">66.170.20.226</a> and<br>
the smtp headers say its from <a href="http://lists.iavit.org" target="_blank">lists.iavit.org</a>. If you lookup<br>
<a href="http://lists.iavit.org" target="_blank">lists.iavit.org</a>, it does resolve to <a href="tel:66.170.20.226" value="+16617020226">66.170.20.226</a>. That should be fine<br>
because if I'm a spammer and I'm using an account on <a href="tel:66.170.20.226" value="+16617020226">66.170.20.226</a>, I'm<br>
going to say I'm somebody *else*. You know, I say I'm<br>
<a href="mailto:Bill.Gates@microsoft.com">Bill.Gates@microsoft.com</a> or something. If you lookup <a href="http://microsoft.com" target="_blank">microsoft.com</a>, you<br>
don't get <a href="tel:66.170.20.226" value="+16617020226">66.170.20.226</a>. Really, just the fact that <a href="http://lists.iavit.org" target="_blank">lists.iavit.org</a> and<br>
<a href="http://iavit.org" target="_blank">iavit.org</a> resolve to the IP address of the smtp client should be enough. How<br>
is a spammer going to fake that? Yeah, I'm sure they could but it would be a<br>
heckuva lot of work.<br>
<br>
There is this SPF record thing where it asks the DNS server for hosts<br>
allowed to send mail for that domain. That makes sense to me. I can<br>
understand that. But I don't get the reverse lookup thing. It seems to me<br>
that would block a lot of legitimate mail for no reason.<br>
<br>
Maybe I'm getting "reverse DNS" mixed up with something else.A forward<br>
lookup is when you take a name and get an IP address from it. Reverse lookup<br>
is when you take the IP and get its name. Right?<br>
<br></blockquote></div>-- <br>-- <br>James P. Kinney III<br><br>As long as the general population is passive, apathetic, diverted to
consumerism or hatred of the vulnerable, then the powerful can do as
they please, and those who survive will be left to contemplate the
outcome.<br>- <i><i><i><i>2011 Noam Chomsky<br><br><a href="http://heretothereideas.blogspot.com/" target="_blank">http://heretothereideas.blogspot.com/</a><br></i></i></i></i><br>