This issue bit me recently since my dns provider (whois.com) just started to enforce no mixing of CNAME and MX records.
The problem I'm having is that I can't figure out a way around this where: (a) both your web services and mail services are hosted (by separate providers), and (b) you want to use the same domain name for mail and web. Specific example is using heroku.com for web hosting and google apps for mail. If my domain is "parasite.com". I want people to be able to go http://parasite.com and u...@parasite.com proxy.heroku.com. A 1.2.3.4 # managed/owned by heroku aspmx.l.google.com. A 1.2.3.4 # managed/owned by google Then it seems all I want/need to do is: parasite.com. CNAME proxy.heroku.com parasite.com. MX aspmx.l.google.com. However, that's exactly what an increasing number of sources are advising against (e.g. http://blogs.eweek.com/cheap_hack/content/dns/dont_mix_mx_and_cname_records.html), and what it seems the DNS providers are starting to come down hard on. So I am at a loss. I think you can get around this by caving on the "same domain" requirement e.g. www.parasite.com. CNAME proxy.heroku.com parasite.com. MX aspmx.l.google.com. or parasite.com. CNAME proxy.heroku.com mail.parasite.com. MX aspmx.l.google.com. But that is _so_ 90's / tail wagging the dog. And it seems we are doing this all because some bad MTA implementations. Any advice from the heroku standpoint? How have others solved this / have I got my analysis correct? Regards, Paul http://tardate.com (for now;-) On Mon, Jun 22, 2009 at 2:28 AM, Jason Eggleston <ja...@eggnet.com> wrote: > > The way I understand DNS, you do not want to have a CNAME record along > with *any* other records for the same name. This includes NS and SOA > records which every domain has. > > For example, if you have a CNAME and MX record for your base domain, > an MX lookup on your domain would result in an MX lookup for > heroku.com. Not good. > > For my domain, I use godaddy to host, point the base at > 64.202.189.170, and set up domain redirecting (301) with godaddy to > the www name. With this service, the whole url is preserved, and www > is appended to the beginning as a 301 redirect, or 302 if you want. > > www is a cname to proxy.heroku.com. Works perfectly. > > If you do it this way even for an existing site, eventually search > engines will direct users to the www version of your domain. > > The only way to use the base domain safely with heroku would be if > heroku started hosting DNS. Google App Engine has the same issue. > > On May 8, 6:36 pm, Adam Wiggins <a...@heroku.com> 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 > > with MX records, 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 heroku@googlegroups.com To unsubscribe from this group, send email to heroku+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/heroku?hl=en -~----------~----~----~----~------~----~------~--~---
