[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] RAQ2 - Still Can't send mail to AOL HELP!
- Subject: Re: [cobalt-users] RAQ2 - Still Can't send mail to AOL HELP!
- From: Jeff Lasman <jblists@xxxxxxxxxxxxx>
- Date: Sun Jan 27 19:06:11 2002
- Organization: nobaloney.net
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
"E.B. Dreger" wrote:
> > Date: Thu, 24 Jan 2002 18:44:00 -0800
> > From: Jeff Lasman <jblists@xxxxxxxxxxxxx>
>
> (snipping throughout)
Is there any reason Eddy, why you're using a post of mine to make your
own, and by extension, look like I'm wrong and you're right? It looks
like we're saying the same thing.
It doesn't look like you're disagreeing with anything I've written, so
I'm wondering.
> > That's because your upstream (whoever provided you your
> > IP#s) did NOT delegate your IP#s to you. I've been pointing
> > out on this list for at least three years that you cannot do
> > your own reverse DNS unless your upstream provider gives you
> > the authority.
>
> DNS debunked: Who cares about "whois". The information there
> isn't worth <insert favorite phrase> when it comes to name
> resolution.
And what has your response got to do with my paragraph? Anything at
all?
> > Yes. Definitely. AOLs behavior in not forwarding mail when
> > there's no reverse DNS is extremely well known and well
> > documented.
>
> Nor is AOL the only one. The most prominent example, perhaps,
> but several sites refuse mail with absent reverse DNS.
As I've written before as well. Is it necessary to talk about the rest
of the world when the specific question is about AOL? Maybe.
> > Either your upstream delegates reverse DNS authority to you, or
> > he does reverse DNS, or you find another provider.
>
> Watch out for upstreams that claim it's a major, expensive
> operation to do. It isn't. If your provider claims that it'll
> take a week and a few hundred dollars, it's time to go shopping.
> Tell them to read RFC 2317.
First of all, if your upstream doesn't have authority they can't
delegate it. Second, if they do have authority, they're responsible for
it being done correctly. Personally considering the sad state of DNS
knowledge among Cobalt/Sun RaQ users I wouldn't automatically delegate
DNS to any of them unless they could prove they have the understanding
to do it right.
Note that I'm NOT blaming any RaQ owner/user. The fact is that Cobalt
doesn't implement it well, and doesn't explain it well, and doesn't
explain well where to go to learn to do it right.
Jeff
--
Jeff Lasman <jblists@xxxxxxxxxxxxx>
Linux and Cobalt/Sun/RaQ Consulting
nobaloney.net
P. O. Box 52672, Riverside, CA 92517
voice: (909) 778-9980 * fax: (702) 548-9484