Well, I tried this (using mail.mydomain.com for MX) and it didn't work
for me on GoDaddy. I think this is just GoDaddy's problem ... they
wouldn't set up an email forwarding address for a subdomain.
Theoretically I think using a subdomain for your email should work,
but I'm giving up on it now, and just using a completely different
domain for email.

It would be great if Heroku could figure out a reliable way to
customize MX records for our CNAME'd domains.

Nate

On Jun 20, 5:52 pm, Nate Clark <[email protected]> wrote:
> I'm struggling with this problem, too.
>
> I was thinking a workaround might be to use a subdomain for your
> MX ... so that you can still use the top-level domain for your
> website. For example, use mail.mydomain.com for sending mail, and keep
> your CNAME pointed to heroku on mydomain.com. I haven't tried this yet
> --- is there any reason why this wouldn't work?
>
> Nate
>
> On Jun 19, 1:54 pm, Erik Pukinskis <[email protected]> wrote:
>
> > Although I guess another solution is just to forward mydomain.com 
> > tohttp://www.mydomain.com/.  Not ideal, but it works.
>
> > Erik
>
> > On Jun 19, 1:48 pm, Erik Pukinskis <[email protected]> wrote:
>
> > > Hi Adam,
>
> > > This doesn't really address the problem.  I'm trying to 
> > > gethttp://sproutrobot.com
> > > pointed at heroku, but if add aCNAMEpointing sproutrobot.com at
> > > proxy.heroku.com, that means I can't add aMXrecord.  Which means I
> > > can't have an email on my domain.
>
> > > As people are discussing, maybe there are some DNS services that let
> > > you mix CNAMEs andMXrecords, but that's advised against in the SMTP
> > > protocol.  And more importantly some mail servers will apparently try
> > > to send mail to the server pointed to by theCNAMErecord.  I'm
> > > guessing that some of Ron's @thumbfight.com email is going to
> > > proxy.heroku.com and getting returned.  
> > > Seehttp://blogs.eweek.com/cheap_hack/content/dns/dont_mix_mx_and_cname_r...
>
> > > Maybe if proxy.heroku.com at least had aMXrecords for gmail that
> > > would help.  Everyone would be locked into gmail, but it's better than
> > > nothing.
>
> > > Best,
> > > Erik
>
> > > On May 8, 6:36 pm, Adam Wiggins <[email protected]> wrote:
>
> > > > Another fix for this is to alias your domain to point to
> > > > proxy.heroku.com instead of heroku.com.  i.e.:
>
> > > > $ host mydomain.com
> > > > mydomain.com is an alias for proxy.heroku.com.
> > > > proxy.heroku.com has address 75.101.145.87
> > > > proxy.heroku.com has address 75.101.163.44
>
> > > > Although it reads a little less nicely, this avoids having to tinker
> > > > withMXrecords, so perhaps we'll make this the official way to set up
> > > > custom domains.  What do you guys think?
>
> > > > Adam
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Heroku" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to