To:
Markus Stumpf <maex-lists-dns-ietf-dnsop@Space.Net>
Cc:
dnsop@cafax.se
From:
Stephane Bortzmeyer <bortzmeyer@nic.fr>
Date:
Fri, 4 Apr 2003 16:45:17 +0200
Content-Disposition:
inline
In-Reply-To:
<20030403152154.B48824@Space.Net>
Sender:
owner-dnsop@cafax.se
User-Agent:
Mutt/1.3.28i
Subject:
Re: RR DNS and spam
On Thu, Apr 03, 2003 at 03:21:54PM +0200, Markus Stumpf <maex-lists-dns-ietf-dnsop@Space.Net> wrote a message of 36 lines which said: > 8.0.30.195.in-addr.arpa IN PTR mail.space.net. > IN TXT "mailto:abuse@space.net" > > That way the maintainers of the RR zone could authorize IPs to be valid > mailservers and receiving mailservers would only accept mails from > sending IPs that have the RR TXT record. I would refuse *any* proposal relying on in-addr.arpa records. Why? Because in many countries (typically all of Africa, except may be RSA), even the ISP have no delegation of the in-addr.arpa space. There are many reasons for that: laziness of the upstream ISP is the most common. But there is also the technical difficulty of delegating in-addr.arpa when the typical allocation is much more specific than a /24. (RFC 2317 is not widely used.) Look at ANRT (Morocco) for instance: they use 194.204.241.128/26 (the object is properly registered in the RIPE database), are fed by the ISP "ONPT" and look at the delegation of the in-addr.arpa... Or look at the Pasteur Institute in Senegal. The IP addresse is 213.154.75.74 (in RIPEland again), The upstream is Sonatel and look at the delegation of the in-addr.arpa... #---------------------------------------------------------------------- # To unsubscribe, send a message to <dnsop-request@cafax.se>.