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 <[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 > 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 [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 -~----------~----~----~----~------~----~------~--~---
