Re: [Asrg] rDNS

Alessandro Vesely <vesely@tana.it> Thu, 28 May 2009 14:16 UTC

Return-Path: <vesely@tana.it>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 05FB43A6D91 for <asrg@core3.amsl.com>; Thu, 28 May 2009 07:16:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.46
X-Spam-Level:
X-Spam-Status: No, score=-0.46 tagged_above=-999 required=5 tests=[AWL=0.259, BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a4-W4PCrBE0o for <asrg@core3.amsl.com>; Thu, 28 May 2009 07:16:50 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by core3.amsl.com (Postfix) with ESMTP id 889FA3A6804 for <asrg@irtf.org>; Thu, 28 May 2009 07:16:37 -0700 (PDT)
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 ale@tana.it, TLS: TLS1.0, 256bits, RSA_AES_256_CBC_SHA1) by wmail.tana.it with esmtp; Thu, 28 May 2009 16:17:44 +0200 id 00000000005DC039.000000004A1E9D08.00002B5F
Message-ID: <4A1E9D1E.20400@tana.it>
Date: Thu, 28 May 2009 16:18:06 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
References: <003d01c9dd01$bf3531d0$800c6f0a@china.huawei.com> <4A1A45BA.5030704@swin.edu.au> <3be421270905250718y5d62f6d5odb6f2bebecf418d0@mail.gmail.com> <4A1D7C8A.5060407@tana.it> <200905271821.OAA20063@Sparkle.Rodents-Montreal.ORG> <728E5AC5-061F-4C93-AFAD-B889195FF0CD@mail-abuse.org> <200905272011.QAA21141@Sparkle.Rodents-Montreal.ORG>
In-Reply-To: <200905272011.QAA21141@Sparkle.Rodents-Montreal.ORG>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] rDNS
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 May 2009 14:16:56 -0000

der Mouse wrote:
>> There are different geographic regions and organizations that refuse
>> to publish reverse DNS.
> 
> This is true.  In my experience being one of them correlates
> positively, and at least moderately strongly (though of course not
> perfectly), with being part of the precipitate.

(as opposed to being part of the "solution", I guess)

Possibly, this scarceness corroborates the belief that rDNS results 
are more trustworthy than direct DNS records.

>> As an anti-abuse effort, some providers [...] do not
>> accept connections without a reverse DNS entry being found.

This used to be typical of FTP servers in the '80s. However, some 
feedback loop providers apparently make use of it today. Let alone 
investigations about the PTR target being automatically generated or 
containing the "dynamic" keyword. IMHO, synthesizing informations on 
that basis is symptomatic of technologies in their infancy being 
desperately greedy for data they cannot obtain [otherwise].

>> As a result, these providers may be unable to communicate with some
>> organizations or geographic regions.
> 
> Right.  So?  Someone who doesn't tolerate dashes in domain names won't
> be able to communicate with rodents-montreal.org, either.

I never heard about dash-intolerants. Are you kidding?

>> Who is wrong, because in the case of email, reverse DNS is clearly
>> being misused.
> 
> It's not clear to me that anyone is wrong there, nor that rDNS is being
> misused.

Much like whois, rDNS is being used in relation with the possibility 
to individuate who, if any, is responsible for running a host at the 
given address. DNSBLs, certificates, reputation, etcetera, all rotate 
around allocations of those IP numbers, but rDNS dependence reveals 
unreadiness for a truly virtual environment: What if _all_ IPs were 
dynamic?