28 May
2015
28 May
'15
7:45 a.m.
On Wed, May 27, 2015 at 5:36 PM, Bryan Fields <Bryan(a)bryanfields.net> wrote:
(Please trim inclusions from previous messages)
_______________________________________________
On 5/27/15 8:33 PM, Don Fanning wrote:
I'd like to try it out then, as I'm certain this doesn't work that way in
most
resolvers for MX's. I've run into it before even.
I can tell you that GMail's MX RR's work in this fashion. I don't need
to
know their A record for my DNS. I just add their CNAME'ed MX records to my
domain files and my mail shows up. And my domain isn't hosted by them.
Just my mail hosting.
https://support.google.com/a/answer/33915?hl=en
> > (Please trim inclusions from previous
messages)
>> > > RFC5321 in Section 5 [http://tools.ietf.org/html/rfc5321#section-5
]
> > states:
>> > >
>> > > "The lookup first attempts to locate an MX record associated with
the
> > name. If
>> > > a CNAME record is found, the
>> > > resulting name is processed as if it were the initial name.*"*
> >
> > This means if the lookup for www.example.com. returns CNAME
example.com,
> > it
> > will use the MX records under example.com., not anything under the
CNAME
>
record www.example.com.
>
>
That is not true at all. The previous paragraph states that it must
process the entire FQDN and not many any inferences as to the domain's
relationship with the FQDN.