I agree, I'd much rather have graphomatic.net be the master address, but there is no way to have a CNAME and MX record for graphomatic.net without breaking the DNS standards and risking not being able to send or receive mail to some hosts.
I'd rather be "so 1999", than break the standards with potentially uncertain consequences. If someone does work out a better way of doing it that doesn't involve breaking the standards I'll happily switch. It would be **really** nice if Heroku could provide DNS services, which could then use the current set of IP addresses, rather than having to use a CNAME. I'd pay a little extra for that service, and it shouldn't require a significant increase in their infrastructure. Currently it's all just a bit too hacky, especially if you need wildcard domains. Paul On Jun 30, 6:49 pm, Erik Pukinskis <erikpukins...@gmail.com> wrote: > Yea, I feel like the Heroku folks must be sympathetic to this, given > thatwww.heroku.comactually redirects to heroku.com. :) > > Erik > > > > On Tue, Jun 30, 2009 at 8:30 AM, Nate Clark<natecla...@gmail.com> wrote: > > > Paul - your setup sounds like it would work, but it's not the solution > > that I'm looking for. I specifically don't want to have "www" in front > > of my domain (that's SO 1999) for web visitors. Correct me if I'm > > wrong, but it appears like there is no way to set up both mail and > > http for the top-level domain on Heroku's setup. Sad ... this is > > making me think twice about hosting my next project on Heroku. > > > Nate > > > On Jun 29, 10:48 am, Paul Leader <paul.lea...@gmail.com> wrote: > >> Just a quick update, > > >> I have now taken my VPS out of the equation (except for mail > >> handling), and am now using GoDaddy's redirection service to redirect > >> fromhttp://graphomatic.nettohttp://www.graphomatic.net > > >> So, in brief, my setup is: > > >> graphomatic.net --> redirects towww.graphomatic.netusingGoDaddy's > >> redirect service. > > >>www.graphomatic.nethasa CNAME record pointing to heroku.com. > > >> graphomatic.net has an MX record pointing to my mail server. > > >> So, web page requests > >> forhttp://www.graphomatic.netandhttp://graphomatic.net > >> both end up at Heroku, and my mail is sent to the correct server. > > >> Not sure if this will work if you need wildcard subdomains, I suspect > >> probably not. > > >> Paul > > >> On Jun 29, 2:09 pm, Paul Leader <paul.lea...@gmail.com> wrote: > > >> > The whole "mixing CNAME's, A and MX records" problem is solvable, but > >> > not without a little something extra. So I thought I'd share my setup > >> > for graphomatic.net. > > >> > Two things to note: > >> > 1) A CNAME record should never be mixed with other records, even if > >> > your DNS provider allows it, the behaviour of mail servers is > >> > undetermined. To quote djb: ``You keep using CNAME records. I do not > >> > think they mean what you think they mean.'' > >> > 2) However, you can have a CNAME record on a sub-domain, the root of > >> > which has other records. > > >> > So, given that to route mail to @graphomatic.net the MX record needs > >> > to be for the base domain, that's where that has to go. Creating an > >> > MX record for mail.graphomatic.net will not do what some people appear > >> > to think it will. It will mean that all e-mail would have to be > >> > addressed to @mail.graphomatic.net, which is almost certainly not what > >> > you want. > > >> > Since the CNAME cannot now be applied to graphomatic.net (as it has an > >> > MX record), it is instead applied towww.graphomatic.net, pointing to > >> > heroku.com. > > >> > So mail will go to wherever you MX record points, andwww.graphomatic.net > >> > works as expected. > > >> > Now, since the CNAME is againstwww.graphomatic.net, we can safely > >> > give graphomatic.net an A record, which points to a server setup to > >> > redirect any request > >> > forhttp://graphomatic.nettohttp://www.graphomatic.net. > > >> > If you have your own server (I have a cheap VPS so that's not a > >> > problem), then you can setup your own redirector. Make it a 301 > >> > permanent redirect to minimise the number of repeat hits. You do not > >> > need a powerful server to handle these redirects. > > >> > If you don't have your own server, then your domain registrar may > >> > provide the ability to redirect. I'm fairly certain that GoDaddy will > >> > allow you to do this. > > >> > After all the above, mail to @graphomatic.net goes to the right place, > >> > and bothhttp://www.graphomatic.netandhttp://graphomatic.netdowhat > >> > you would expect them to do. And it's all done without having to > >> > bodge your DNS with on-standard mixes of records, risking non-delivery > >> > of mail. > > >> > Paul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
