Reverse DNS and RFC 2317

[Gary Wardell]

Hi,

But in my case, and the reason I posed this question, I have a few services 
running, one of them being a mail server running at mail.yeshua.cc.

The ISP I am currently at has virtually nothing in the in-addr.arpa for the 
class C block than my 16 ips are in.

Another ISP that I talked to, thinking of moving, said that they don't 
delegae and that they wouldnlt put my mserver name in either.  That they 
only use generic name like dsl.max63.isp.net.  While my forward would be 
mail.yeshua.cc which also apears on my MX.  The second ISP almost guranteed 
that I wouldn't have any trouble with their setup.

So. if the reciveing MTA is checking for a matchiung name in the MX record 
and the existance of a reversx PTR then I'm ok, right?

BTW, I think your right that my current upstream ISP doesn't have a clue 
about several things.

Gary


On Thursday, May 18, 2000 12:07 AM, Don Stokes 
[SMTP:don at news.daedalus.co.nz] wrote:
> Len Conrad  <lconrad at go2france.com> wrote:
> >More and more mail servers are performing these kinds of DNS 
validations,
> >so the reverse delegation and PTR records of at least a mail server are
> >increasingly important for reliable mail delivery.
>
> You don't need the reverse maps *delegated*, you just need them to be
> there.  It's fine if the ISP provides their own names, eg
> ip-99-88-77-66.isp.net for 66.77.88.99.in-addr.arpa, as long as both
> forward and reverse maps are present and consistent.
>
> An ISP that doesn't do *something* with its reverse maps is
> demonstrating insufficient clue to be an ISP, IMAO.
>
> -- don
>
>