Ok, so we all agree that it is not a good idea to use CNAME for the root domain, but if I wanted to bring the focus back towards finding a solution, what then?
Heroku is providing me an entry point of proxy.heroku.com and is strongly discouraging the use of A records (see http://docs.heroku.com/custom-domains where the note pic is): "Why can't you use an A record, which is a hard-coded IP address? Heroku is a cloud computing provider, and our front-end load balancers will change IPs from time to time. When they do, any apps hard-coded to point at a specific IP, instead than proxy.heroku.com, will stop working. So we strongly discourage you from using A records." But according to the RFC regulations, the following records will potentially or most likely cause problems, because the MX records could be ignored as the root domain is configured with a CNAME rather than as an A record: mydomain.com. MX 10 aspmx.l.google.com. mydomain.com. MX 20 alt1.aspmx.l.google.com. mydomain.com. MX 20 alt2.aspmx.l.google.com. mydomain.com. MX 30 aspmx2.googlemail.com. mydomain.com. MX 30 aspmx3.googlemail.com. mydomain.com. MX 30 aspmx4.googlemail.com. mydomain.com. MX 30 aspmx5.googlemail.com. mail CNAME ghs.google. mydomain.com. CNAME proxy.heroku.com. www CNAME proxy.heroku.com. Is there any solution that might work? What would you do if you had to set the website up for Heroku while keeping the emails alives? - JM --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to rails-oceania@googlegroups.com To unsubscribe from this group, send email to rails-oceania+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~----------~----~----~----~------~----~------~--~---
