OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: "cannot find your hostname", but DNS lookups are fine

From: mouss (usebsdfree.fr)
Date: Wed Oct 12 2005 - 06:36:24 CDT


Ben Finney a écrit :

>On 12-Oct-2005, Ralf Hildebrandt wrote:
>
>
>>* Ben Finney <benbenfinney.id.au>:
>>
>>
>>
>>>Oct 12 14:37:37 protea postfix/smtpd[32733]: NOQUEUE: reject: RCPT from unknown[150.101.164.6]: 450 Client host rejected: cannot find your hostname, [150.101.164.6]; from=<squawkcorax.com.au> to=<benbenfinney.id.au> proto=ESMTP helo=<nest.corax.com.au>
>>>
>>>
>>mail:~# host 150.101.164.6
>>Name: eth164-6.vic.adsl.internode.on.net
>>Address: 150.101.164.6
>>
>>mail:~# host eth164-6.vic.adsl.internode.on.net
>>eth164-6.vic.adsl.internode.on.net does not exist (Authoritative answer)
>>
>>
>
>Thanks.
>
>If the hostname lookup succeeds, what results will satisfy the
>reject_unknown_hostname restriction?
>
reject_unknown_hostname has nothing to do with client IP or rdns. It
rejects an unknown helo. postfix 2.3 changes the name to
"reject_unknown_helo_hostname" to avoid the confusion with
reject_unknown_client_hostname.

>If multiple A records exist with
>different addresses, will the check pass?
>
>
>
- given the client IP (which is obtained from the socket), get all names
(ptr)
- for each name, get all IPs (A). if one of these IPs matches the client
IP, we're done. else ignore name.